Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Hi. I have this program:
#include
void tst(void)
{
float x;
scanf("%f", x);
}
I compile and I see this:
$ gcc-14 -Wall -Wextra -c -o t
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Created attachment 57827
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57827&action=edit
Reduced reproducer
I git a bug in gcc 13.2 where an openmp loop causes he comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100
--- Comment #4 from Dima Kogan ---
I just tried again, and I see that this bug has been fixed. I'm using
gcc (Debian 13.2.0-2) 13.2.0
Should we close this report?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97261
--- Comment #3 from Dima Kogan ---
Hi. Thanks for replying. I don't the warning that I'm claiming is bogus is
complaining about the points you raised. If it did, then making g() static or
building without -fPIC or -O3 wouldn't make the warning go
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97261
--- Comment #1 from Dima Kogan ---
Created attachment 49294
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49294&action=edit
Code to demo the issue
: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Hi. I'm seeing gcc-10 flag a warning that I'm pretty sure is incorrect. gcc-9
and older did not warn about this (although that's probably because they
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Created attachment 48716
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48716&action=edit
Bug demo
Hi. I'm running gcc-10 from Debian:
dima@s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80824
--- Comment #2 from Dima Kogan ---
I just tried this with Debian builds of gcc8 and gcc9: 8.3.0-19 and 9.2.1-8.
This bug still exists in both.
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Created attachment 41387
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41387&action=edit
test case
Hi.
I'm using gcc 7.1.0 from Debia
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100
--- Comment #2 from Dima Kogan ---
For easier reading, the test program looks like this:
#include
extern int s[];
int s[] = { 1,2,3 };
int main(void)
{
printf("%zd\n", sizeof(s));
return 0;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100
--- Comment #1 from Dima Kogan ---
Created attachment 39876
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39876&action=edit
test case
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Hi.
I'm using gcc 6.2 from Debian on an amd64 machine:
dima@fatty:/tmp$ gcc --version
gcc (Debian 6.2.0-9)
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Target Milestone: ---
Created attachment 36072
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36072&action=edit
Minimized source to show the failure
Hi. I'm seeing an internal compile
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Hi. I'm running gcc-4.9.1 from Debian/sid. This is built off of r214759. When
building source that had a mistake GCC produced a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
Dima Kogan changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
--- Comment #9 from Dima Kogan ---
For the record, here's the ccache bug I just filed:
https://bugzilla.samba.org/show_bug.cgi?id=10819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
Dima Kogan changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
--- Comment #5 from Dima Kogan ---
Hi.
I cherry-picked the commit you mentioned, rebuilt gcc, and the bug was not
resolved. Just in case I did something wrong in that process, I waited for
Debian to update their package. This just happened, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
--- Comment #4 from Dima Kogan ---
Hi. Thank you for looking at this. I'm not set up to make bleeding-edge gcc
builds, so let me wait until Debian catches up, and I'll report back. Currently
they're on r214759 (not what the bug report mentions, b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
--- Comment #2 from Dima Kogan ---
Created attachment 33452
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33452&action=edit
and the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63178
--- Comment #1 from Dima Kogan ---
Created attachment 33451
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33451&action=edit
The source to show the issue
iority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gccbugs at dima dot secretsauce.net
Hi. I'm seeing that under particular conditions I can pass a wrong type into a
function, and no warning results. I'm attaching a minimized test case to show
this.
22 matches
Mail list logo
