[Bug c/55976] -Werror=return-type should error on returning a value from a void function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976 Dave Pagan changed: What|Removed |Added Keywords||patch --- Comment #9 from Dave Pagan --- Patch submitted for review: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg01034.html
[Bug c/55976] -Werror=return-type should error on returning a value from a void function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976 --- Comment #12 from Dave Pagan --- New test pr55976-1.c is failing due to unaccounted for extraneous output from the compiler. Test requires addition of dg-prune-output. Adding the directive and will send patch shortly.
[Bug c/55976] -Werror=return-type should error on returning a value from a void function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976 --- Comment #15 from Dave Pagan --- Thanks, Paolo! On 06/28/2018 01:44 AM, paolo.carlini at oracle dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976 > > Paolo Carlini changed: > > What|Removed |Added > > Status|ASSIGNED|RESOLVED > Resolution|--- |FIXED > Target Milestone|--- |9.0 > > --- Comment #14 from Paolo Carlini --- > Done. I think we can close the bug as fixed in trunk. >
[Bug c/46921] Dropped side effect with combination of statement expression and struct initializer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46921 Dave Pagan changed: What|Removed |Added CC||dave.pagan at oracle dot com --- Comment #1 from Dave Pagan --- If no one is working on this, I'd like to take a look into it.
gcc-bugs@gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30552 Dave Pagan changed: What|Removed |Added CC||dave.pagan at oracle dot com --- Comment #4 from Dave Pagan --- It appears this is a case where ICEs are the result of poor error detection/recovery with statement expressions in these contexts. Has anyone else looked into this? If not, I'd like to investigate it further to verify what I'm seeing and come up with a solution.
gcc-bugs@gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30552 --- Comment #6 from Dave Pagan --- (In reply to Eric Gallager from comment #5) > (In reply to Dave Pagan from comment #4) > > It appears this is a case where ICEs are the result of poor error > > detection/recovery with statement expressions in these contexts. Has anyone > > else looked into this? If not, I'd like to investigate it further to verify > > what I'm seeing and come up with a solution. > > Not that I know of; please go ahead! Great. Thanks for the quick response, Eric.
gcc-bugs@gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30552 --- Comment #12 from Dave Pagan --- Yes, it did. I had assumed the bug status would get updated, but it wasn't. I'll set it to resolved.
gcc-bugs@gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30552 Dave Pagan changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #13 from Dave Pagan --- Fixed with patch noted in comments: https://gcc.gnu.org/ml/gcc-patches/2018-03/msg00621.html
[Bug c/46921] Lost side effect when struct initializer expression uses comma operator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46921 Dave Pagan changed: What|Removed |Added Summary|Dropped side effect with|Lost side effect when |combination of statement|struct initializer |expression and struct |expression uses comma |initializer |operator --- Comment #3 from Dave Pagan --- When emitting initializer elements (output_init_element), the left hand expression of a comma operator with result size zero is not evaluated. It should be, however, if the expression is marked as having side effects.
[Bug c/46921] Lost side effect when struct initializer expression uses comma operator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46921 --- Comment #4 from Dave Pagan --- Patch submitted for review: https://gcc.gnu.org/ml/gcc-patches/2018-02/msg01471.html
gcc-bugs@gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30552 --- Comment #8 from Dave Pagan --- Patch submitted for review: https://gcc.gnu.org/ml/gcc-patches/2018-03/msg00621.html
[Bug c/55976] -Werror=return-type should error on returning a value from a void function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976 Dave Pagan changed: What|Removed |Added CC||dave.pagan at oracle dot com --- Comment #4 from Dave Pagan --- If no one is working on this, I'd like to take a look into it.
[Bug c/39808] warn_unused_result fails to produce warning in a statement expression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39808 Dave Pagan changed: What|Removed |Added CC||dave.pagan at oracle dot com --- Comment #5 from Dave Pagan --- Anyone looking at this? If not, I'd like to.
[Bug c/55976] -Werror=return-type should error on returning a value from a void function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976 --- Comment #6 from Dave Pagan --- Helpful update, Jonathan - did you want to follow up on this bug then? Or should I go ahead based on your new information?
[Bug c/81568] attribute always_inline honored even after attribute noinline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81568 Dave Pagan changed: What|Removed |Added CC||dave.pagan at oracle dot com --- Comment #2 from Dave Pagan --- Martin, have you (or has anyone else) spent time on this, or have a fix already? I was thinking about looking into it further but don't want to duplicate effort.
[Bug c/81568] attribute always_inline honored even after attribute noinline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81568 --- Comment #5 from Dave Pagan --- Thanks for the update, Martin.
