bpo-30923: Silence fall-through warnings included in -Wextra since gc…#3157
bpo-30923: Silence fall-through warnings included in -Wextra since gc…#3157skrah merged 1 commit intopython:masterfrom skrah:fallthrough
Conversation
| *pinoutmask |= (1 << i); /* mark as inout arg */ | ||
| (*pnumretvals)++; | ||
| /* fall through to PARAMFLAG_FIN... */ | ||
| /* fall through */ |
There was a problem hiding this comment.
Why existing comments are shortened?
There was a problem hiding this comment.
gcc only recognizes "fall through" (and a couple of other versions), but not that comment with additional words.
I only changed comments that aren't recognized.
| else if (o == Py_False) | ||
| return 0; | ||
| } | ||
| /* fall through */ |
There was a problem hiding this comment.
Wouldn't be better to move this comment one line up, inside a block, and align it with if and else? And add "else" before "fall through".
There was a problem hiding this comment.
Agreed, but gcc doesn't recognize that. It's pretty inflexible.
|
Thanks everyone! |
|
Just checking out the bot, this is fantastic. |
|
Thanks @skrah Seems like there was problem backporting. I will try this again. |
|
Sorry @skrah and @skrah, I had trouble checking out the backport branch.Please backport using cherry_picker on command line. |
|
Sorry, @skrah and @skrah, I could not cleanly backport this PR due to a conflict.Please backport using cherry_picker on command line. |
|
Okay, thanks! I suspected there would be too many conflicts. So let's not backport this, it isn't worth the trouble. |
…nce gcc-7.0 (#3518) * bpo-30923: Disable warning that has been part of -Wextra since gcc-7.0. (#3142) (cherry picked from commit d73a960) * bpo-30923: Silence fall-through warnings included in -Wextra since gcc-7.0. (#3157) (cherry picked from commit f432a32) * bpo-31275: Small refactoring to silence a fall-through warning. (#3206) (cherry picked from commit 138753c)
7 participants
…c-7.0.
https://bugs.python.org/issue30923