This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | matrixise |
|---|---|
| Recipients | cstratak, matrixise, serhiy.storchaka, skrah, vstinner, zach.ware |
| Date | 2017年07月25日.14:22:49 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1500992569.11.0.933113706854.issue30923@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I am not for a backport, it's not a security fix or a bug fix. for my case, I just want to "kill" the warnings, maybe we could check the version of gcc and add "-Wimplicit-fallthrough=0". Here is a good explanation of the 'fallthrough' in gcc7 https://developers.redhat.com/blog/2017/03/10/wimplicit-fallthrough-in-gcc-7/ |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年07月25日 14:22:49 | matrixise | set | recipients: + matrixise, vstinner, skrah, zach.ware, serhiy.storchaka, cstratak |
| 2017年07月25日 14:22:49 | matrixise | set | messageid: <1500992569.11.0.933113706854.issue30923@psf.upfronthosting.co.za> |
| 2017年07月25日 14:22:49 | matrixise | link | issue30923 messages |
| 2017年07月25日 14:22:49 | matrixise | create | |