: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40530
--- Comment #2 from h dot b dot furuseth at usit dot uio dot no 2008-11-17
20:15 ---
Subject: Re: [4.4 regression] #elif non-const expression #defined in this
#if breaks
Yes, I should have read the #36320 text more carefully. I merely
noticed that its empty #elif cannot expand
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build triplet: i386-redhat-linux
GCC host triplet: i386-redhat-linux
GCC target triplet: i386-redhat-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36887
--- Comment #1 from h dot b dot furuseth at usit dot uio dot no 2008-07-21
11:36 ---
Subject: Re: New: Please report #pragma GCC poison location
Sorry about the empty report. Anyway:
The warning
a.c:2:5: attempt to use poisoned foo
is not intelligle if one does not know about
warnings
Product: gcc
Version: 4.2.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build
--- Comment #22 from h dot b dot furuseth at usit dot uio dot no
2007-08-20 22:45 ---
Subject: Re: warn for uninitialized arrays passed as const* arguments
manu at gcc dot gnu dot org writes:
But it seems that the current policy of GCC is to not assume that such
functions actually
--- Comment #1 from h dot b dot furuseth at usit dot uio dot no 2007-01-13
18:40 ---
The warning is a bit misleading,
function might be possible candidate for 'printf' format attribute
means the _calling_ function might be such a candidate, not the function
being called on the line
, invalid)
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build
--- Comment #2 from h dot b dot furuseth at usit dot uio dot no 2006-12-19
11:27 ---
Subject: Re: -fno-inline-functions does not work, and doc bugs
pinskia at gcc dot gnu dot org writes:
You want -fno-inline-functions-called-once which was added in 4.2.0
IIRC (...)
I see
--- Comment #3 from h dot b dot furuseth at usit dot uio dot no 2006-12-19
11:31 ---
Subject: Re: -fno-inline-functions does not work, and doc bugs
I just noticed another doc bug:
http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#Optimize-Options
That page says:
-O2
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30240
--- Comment #2 from h dot b dot furuseth at usit dot uio dot no 2006-12-03
15:49 ---
Subject: Re: [4.0/4.1 Regression] while(__builtin_expect()) pessimizes loop
pinskia at gcc dot gnu dot org writes:
Fixed for 4.2.0:
(...)
Status|UNCONFIRMED |RESOLVED
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30054
furuseth at usit dot uio dot no
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30055
--- Comment #7 from h dot b dot furuseth at usit dot uio dot no 2006-10-24
08:20 ---
Subject: Re: Issues with -Wchar-subscripts
gdr at integrable-solutions dot net writes:
The absence of warning in C is OK -- literal characters have type int
in C.
Yes, but see previous comments
array index
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build
--- Comment #5 from h dot b dot furuseth at usit dot uio dot no 2006-10-17
12:49 ---
Subject: Re: Issues with -Wchar-subscripts
pinskia at gcc dot gnu dot org writes:
'a' in C is not of the type char but instead int so not warning
there is correct really.
How about a -Warray
--- Comment #2 from h dot b dot furuseth at usit dot uio dot no 2006-10-14
17:06 ---
Subject: Re: Issues with -Wchar-subscripts
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29455
--- Comment #3 from h dot b dot furuseth at usit dot uio dot no 2006-10-14
17:52 ---
Subject: Re: Issues with -Wchar-subscripts
Sorry about the empty answer.
pinskia at gcc dot gnu dot org writes:
'a' in C is not of the type char but instead int so not warning there
is correct
: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla
--- Comment #4 from h dot b dot furuseth at usit dot uio dot no 2005-11-02
19:52 ---
I think I'd appreciate that warning when writing portable code:
The warning can be useful if the 1 is replaced with a macro
which may or may not expand to 1, or an enum defined in an #ifdef
: unassigned at gcc dot gnu dot org
ReportedBy: h dot b dot furuseth at usit dot uio dot no
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla
24 matches
Mail list logo
