-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__attribute__((fallthrough)) with braces #22
base: master
Are you sure you want to change the base?
Conversation
Accept braces (cases 12 and 13)
This is an unofficial mirror that nobody from the GCC project is involved with. Sending pull requests here is a waste of time. Please see https://gcc.gnu.org/contribute.html for how to contribute to GCC, thanks. |
Then what's the point to have a GitHub presence if nothing can be done from there since "nobody from the GCC project is involved with" as you put it mildly ? Regarding the link, it starts with an annoying "Legal Prerequisites" stating that "FSF prefers that a contributor files a copyright assignment". If that's the way the mighty FSF welcomes contributors, it, in contrary, effectively turns me down and puts an end to my willing collaboration and hence they might receive my warmest finger salute. |
You seem to be missing the point that this mirror was created by an unknown person who has nothing to do with the GCC project. Anybody can create a fork of any open source Git repo and host it on github. This is not "a Github presence" for the GCC project, it's just a repo created by a person on the internet. If you don't want to contribute to GCC that's fine, there's no need to be rude about it. |
Something called gcc-mirror and mirroring the official repo looks legit enough to be thought having some affiliation with the original content, hence my believing participating here might have some impact on the other side of the bridge it is connected to. If not, I see no point to this repo and getting people fooled into something that is then just a scam. Should I warn the gcc guys and github staff about this place ? |
@Kochise you don't have to sign anything. The following paragraph from contribute page makes it clear for you:
|
@Kochise How did it go? |
Dunno, I abandoned all hope into gcc and carried on another more faithful path. |
This is the first pass at implementing macros more testcases are needed. This does not support repetition matchers but it supports simple declarative macros and transcribes them. The approach taken here is that we reuse our existing parser to call the apropriate functions as specified as part of the MacroFragmentType enum if the parser does not have errors parsing that item then it must be a match. Then once we match a rule we have a map of the token begin/end offsets for each fragment match, this is then used to adjust and create a new token stream for the macro rule definition so that when we feed it to the parser the tokens are already substituted. The resulting expression or item is then attached to the respective macro invocation and this is then name resolved and used for hir lowering. Fixes gcc-mirror#17 gcc-mirror#22 Addresses #573
938: First pass at declarative macro expansion r=philberty a=philberty This does not support repetition matchers but it supports simple declarative macros and transcribes them. The approach taken here is that we reuse our existing parser to call the apropriate functions as specified as part of the MacroFragmentType enum if the parser does not have errors parsing that item then it must be a match. Then once we match a rule we have a map of the token begin/end offsets for each fragment match, this is then used to adjust and create a new token stream for the macro rule definition so that when we feed it to the parser the tokens are already substituted. The resulting expression or item is then attached to the respective macro invocation and this is then name resolved and used for hir lowering. Fixes gcc-mirror#17 gcc-mirror#22 Addresses #573 Co-authored-by: Philip Herron <philip.herron@embecosm.com>
Add support for const attribute in libgccjit
Accept braces (cases 12 and 13)