https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96739
--- Comment #3 from Dr. David Alan Gilbert ---
Hi Martin,
Thanks for the response.
I've added a slightly less boiled down test that I think is still valid.
I agree with that you say in the case of the call from help_all->help_oneline
because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96739
--- Comment #2 from Dr. David Alan Gilbert ---
Created attachment 49108
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49108=edit
less boiled down test
Assignee: unassigned at gcc dot gnu.org
Reporter: dgilbert at redhat dot com
Target Milestone: ---
Created attachment 49096
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49096=edit
boiled down test file
The following is boiled down (too far?) from curr
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dgilbert at redhat dot com
Target Milestone: ---
gcc version 9.0.1 20190312 (Red Hat 9.0.1-0.10) (GCC)
on Fedora 30, x86-64
We tripped over code like this in qemu which seems obvious
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Dr. David Alan Gilbert changed:
What|Removed |Added
CC||dgilbert at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #9 from Dr. David Alan Gilbert ---
(In reply to Paolo Bonzini from comment #8)
> g_assertion_message_cmpnum is not declared anymore as noreturn since glib
> 2.38.
> https://bugzilla.gnome.org/show_bug.cgi?id=692125 :-O
!!!? Oh in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #7 from Dr. David Alan Gilbert ---
(In reply to Martin Sebor from comment #6)
> The reduced test case from comment #4 doesn't trigger a warning because in
> it the value of n is unknown. The original test case does trigger it
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #2 from Dr. David Alan Gilbert ---
Created attachment 41147
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41147=edit
a different signed/size case
Here's another case (law said to attach it to the same bug), this is giving:
In
Assignee: unassigned at gcc dot gnu.org
Reporter: dgilbert at redhat dot com
Target Milestone: ---
Created attachment 41146
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41146=edit
source file that triggers warning
The attached code (from QEMU's test suite) triggers the follow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69825
--- Comment #1 from Dr. David Alan Gilbert ---
Oops, forgot to mention; this is on fedora 23 x86-64.
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dgilbert at redhat dot com
Target Milestone: ---
gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC)
$ cat bug.c
void bug(void)
{
static unsigned int counter = 0;
static const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64614
--- Comment #8 from Dr. David Alan Gilbert dgilbert at redhat dot com ---
Richard: Thanks for the fix, and apologies again for my screwed up regression
test.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64614
Dr. David Alan Gilbert dgilbert at redhat dot com changed:
What|Removed |Added
Summary|bogus used initialized |bogus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64614
--- Comment #2 from Dr. David Alan Gilbert dgilbert at redhat dot com ---
(In reply to Marek Polacek from comment #1)
We have tons of these -W*uninitialized bugs, so there's likely a dup.
Yep, it's possible - I couldn't find an obvious match
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dgilbert at redhat dot com
gcc t.c -O1 -Wall -Wextra
(Any -O value 1 or above)
t.c: In function ‘foo’:
t.c:15:15: warning: ‘tmp’ may be used uninitialized
15 matches
Mail list logo
