[Bug c/57182] New: Documentation implies -fprofile-arcs required to create .text.unlikely sections

2013-05-05 Thread rusty at rustcorp dot com.au
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57182 Bug #: 57182 Summary: Documentation implies -fprofile-arcs required to create .text.unlikely sections Classification: Unclassified Product: gcc Version: unknown

[Bug c/57182] Documentation implies -fprofile-arcs required to create .text.unlikely sections

2013-05-06 Thread rusty at rustcorp dot com.au
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57182 --- Comment #2 from rusty at rustcorp dot com.au 2013-05-06 07:59:02 UTC --- Sure, once I understood how it worked, I could parse the documentation. But that's a bit backwards :) Thanks, Rusty.

[Bug c/86584] New: Incorrect -Wsequence-point warning on structure member

2018-07-18 Thread rusty at rustcorp dot com.au
Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rusty at rustcorp dot com.au Target Milestone: --- gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0, x86-64. Also in gcc-8 (Ubuntu 8.1.0-1ubuntu1) 8.1.0. I have a macro which does an assignment, and also hands the address of the

[Bug c/67793] New: Detect incorrect function arg sizes at compile time.

2015-09-30 Thread rusty at rustcorp dot com.au
Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rusty at rustcorp dot com.au Target Milestone: --- It would be great if GCC warned on this: extern int func_(char x[32]); int main(int argc, char *argv[]) { char p[8]; return func(p); } Failing

[Bug c/66425] New: (void) cast doesn't suppress __attribute__((warn_unused_result))

2015-06-04 Thread rusty at rustcorp dot com.au
ement Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rusty at rustcorp dot com.au Target Milestone: --- Yes, a repeat of 2005's https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25509 The world, especially glibc and the Linux ke

[Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))

2015-06-10 Thread rusty at rustcorp dot com.au
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 --- Comment #3 from rusty at rustcorp dot com.au --- Indeed, cast to void has been a standard "I really want to ignore this" notation. It's intuitive and obvious, and ISTR seeing it in the early 90s for lint warning suppression, for example.

[Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))

2015-06-14 Thread rusty at rustcorp dot com.au
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 --- Comment #19 from rusty at rustcorp dot com.au --- I like WUR as a sanity-check, and it is useful that more and more library authors are using it (generally quite well). As Andrew points out, this has taken 10 years! The downside is that

[Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))

2015-08-19 Thread rusty at rustcorp dot com.au
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 --- Comment #21 from rusty at rustcorp dot com.au --- jengelh at inai dot de writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 > > --- Comment #20 from Jan Engelhardt --- > Seems like the short route is to add a n

[Bug c/76733] New: GCC should warn on repeated initializer for same array element / struct member.

2016-08-14 Thread rusty at rustcorp dot com.au
: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rusty at rustcorp dot com.au Target Milestone: --- Hit a nasty cut & paste bug in my code (extra comma before +3): int x[] = { [0] = 1, +3, [1] = 1 }; This do

[Bug c/76732] GCC should warn on repeated initializer for same array element / struct member.

2016-08-16 Thread rusty at rustcorp dot com.au
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76732 --- Comment #6 from rusty at rustcorp dot com.au --- "manu at gcc dot gnu.org" writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76732 > > Manuel López-Ibáñez changed: > >What|Removed

[Bug c/106424] New: __attribute__ unused confuses -Wshadow when placed on internal parameter of fn ptr

2022-07-23 Thread rusty at rustcorp dot com.au via Gcc-bugs
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rusty at rustcorp dot com.au Target Milestone: --- OK, this is a weird one. I have some automated code which adds attributes and it (overzealously) added it to the

[Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))

2023-04-23 Thread rusty at rustcorp dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 --- Comment #47 from rusty at rustcorp dot com.au --- Civility please. We're all trying to find a path to improve things here. But accept that the conversation on this issue is only a weak indication of consensus. As Andrew Pinski says &q

[Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))

2024-07-22 Thread rusty at rustcorp dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 --- Comment #81 from rusty at rustcorp dot com.au --- (In reply to Jakub Jelinek from comment #76) > (void) casts not quieting the warning was an intentional request when the > warning has been added, I really don't think it is a g

[Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))

2024-07-23 Thread rusty at rustcorp dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 --- Comment #83 from rusty at rustcorp dot com.au --- > Then they shouldn't use warn_unused_result! The documentation of that is > very very clear: both about what it does, and about what situations it is > meant for. P