http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54807
Bug #: 54807
Summary: Names declared in a for's for-init-statement and
condition should be in the same declarative region
Classification: Unclassified
Product: gcc
Versi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54807
--- Comment #2 from Ulf Magnusson 2012-10-04
04:57:42 UTC ---
Could very well be the same problem, but I don't have 4.7 handy to confirm.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47130
Summary: Problem with macro expansion in GDB when using PCHs
and #including .cpp files
Product: gcc
Version: 4.4.3
Status: UNCONFIRMED
Severity: normal
Priority: P
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47130
--- Comment #2 from Ulf Magnusson 2010-12-30
21:30:47 UTC ---
(In reply to comment #1)
> presumably component should be "pch" or "c++" ... not "c" though
Didn't notice the "pch" category - sorry about that.
nhancement
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ulfalizer at gmail dot com
This would detect e.g. ptr == '\0' when *ptr == '\0' was intended, which could
be very dangerous (and just bit me).
This might be tric
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64767
--- Comment #2 from Ulf Magnusson ---
Looks like -Wnon-literal-null-conversion is intended to warn for the comparison
case too, though it doesn't seem to be implemented yet as of clang 3.4:
http://llvm.org/klaus/clang/commit/50800fc551ac6b8a95cca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64767
--- Comment #3 from Ulf Magnusson ---
clang also generates a warning for C programs with void *a = '\0' by the way,
so it seems to be able to look at the form of the integral constant there.
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: ulfalizer at gmail dot com
The warning
posix_memalign_warn.c: In function ‘f’:
posix_memalign_warn.c:9:5: warning: ‘ptr’ may be used uninitialized in this
function [-Wmaybe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244
--- Comment #1 from Ulf Magnusson ---
This warning did not occur for GCC 4.8.2 (or whatever the most recent GCC
version is on Ubuntu 14.04) by the way.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244
--- Comment #4 from Ulf Magnusson ---
Created attachment 34894
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34894&action=edit
-Wmaybe-uninitialized-warning with -Og with GCC 4.9.1
The testcase was in the comment. I'm attaching it.
I don
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244
--- Comment #6 from Ulf Magnusson ---
Comment on attachment 34894
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34894
-Wmaybe-uninitialized-warning with -Og with GCC 4.9.1
void exit(int __status) __attribute__ ((__noreturn__));
int posix_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244
--- Comment #7 from Ulf Magnusson ---
Created attachment 34895
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34895&action=edit
Headerless version
Sorry -- thought my previous action would edit the attachment directly.
I've now attached a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244
--- Comment #9 from Ulf Magnusson ---
Created attachment 34897
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34897&action=edit
Reduce testcase using __builtin_posix_memalign().
The warning goes away with -fno-builtin. I didn't realize pos
omponent: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ulfalizer at gmail dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: FreeBSD 5.4-RELEASE i386
GCC host triplet: FreeBSD 5.4-RELEASE i386
GCC target triplet: FreeBSD 5.4-RELEASE
14 matches
Mail list logo
