Severity: minor
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 triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
--- 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,
quot;, 10, __PRETTY_FUNCTION__),
0)));
}
--
Summary: assert(i) gives "will never be executed" due to noreturn
Product: gcc
Version: 4.0.1
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: c
AssignedTo: unassi
(-1)/2 overflow 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 do
t gnu 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 on
--- 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 co
D
Severity: minor
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 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
.254s
user0m0.252s
sys 0m0.001s
--
Summary: while(__builtin_expect()) pessimizes loop
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot
--- 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|UN
ONFIRMED
Severity: normal
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 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-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 (...)
--- 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:
--- 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
bein
t"
va_end(ap);
}
--
Summary: Please warn about va_start(ap, invalid)
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu do
not functioning under Interix 3.5
Product: gcc
Version: 3.3
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: j dot b dot o dot s dot martens at tue
101 - 116 of 116 matches
Mail list logo
