[Bug c/82134] warn_unused_result triggers on empty structs even when they are used

2021-05-15 Thread dblaikie at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82134 David Blaikie changed: What|Removed |Added CC||dblaikie at gmail dot com --- Comment

[Bug c/82134] warn_unused_result triggers on empty structs even when they are used

2017-11-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82134 --- Comment #5 from Jakub Jelinek --- I don't argue that returning empty structures can be sometimes useful. But I fail to understand why would you want to use warn_unused_result attribute on such functions, that just makes no sense, because

[Bug c/82134] warn_unused_result triggers on empty structs even when they are used

2017-11-13 Thread arvo at me dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82134 Arne Vogel changed: What|Removed |Added CC||arvo at me dot com --- Comment #4 from

[Bug c/82134] warn_unused_result triggers on empty structs even when they are used

2017-09-07 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82134 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment

[Bug c/82134] warn_unused_result triggers on empty structs even when they are used

2017-09-07 Thread zackw at panix dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82134 --- Comment #2 from Zack Weinberg --- The claim in the Stack Overflow post was that this was useful in a scenario involving machine-generated code that couldn't return void for some external reason, but they didn't go into any kind of detail.

[Bug c/82134] warn_unused_result triggers on empty structs even when they are used

2017-09-07 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82134 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1