https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
Szabolcs Nagy changed:
What|Removed |Added
CC||nszabolcs at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136
--- Comment #12 from Szabolcs Nagy ---
geniterators.sh was new in gcc-5 and the first version of the script already
used \n in the sed replacement pattern (and other gnu extensions too).
shall i backport the new script to the gcc-5 branch?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66322
Szabolcs Nagy changed:
What|Removed |Added
CC||nszabolcs at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136
--- Comment #8 from Szabolcs Nagy ---
the new awk version is supposed to produce the exact same output as the old
script with gnu sed.
the pasted output fragment looks ok.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136
--- Comment #5 from Szabolcs Nagy ---
patch that uses awk:
https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01578.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136
--- Comment #2 from Szabolcs Nagy ---
the posix standard does not seem to disallow \n in the replacement string so i
think freebsd sed should be fixed (or report the bug to the austingroup).
meanwhile i will prepare a fix for this in gcc.
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nszabolcs at gmail dot com
in the following simple testcase the valid length of x.a+1 is 1, but 2 is
passed to __strcpy_chk according to the asm (gcc-4.8 gets it right, glibc
debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451
Szabolcs Nagy changed:
What|Removed |Added
CC||nszabolcs at gmail dot com
--- Comment
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nszabolcs at gmail dot com
In the following example gcc should be able to prove that
x may be uninitialized, but it does not warn.
$ gcc-4.8 -c -O2 -Wmaybe-uninitialized example.c
$ cat
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nszabolcs at gmail dot com
gcc emits incorrect warning for inline function with internal linkage:
$ cat example.c
static int n;
static inline int f(void);
inline int f
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nszabolcs at gmail dot com
Target: i686-pc-linux-gnu
with -fexcess-precision=standard extra load and store is generated
on i386 linux even when it is not needed
(the code is correct but does unnecessary work on
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nszabolcs at gmail dot com
unused variable warnings are incorrectly issued for
volatile variables
a volatile variable is only unused if it is not
accessed, otherwise code will be generated for
--- Comment #130 from nszabolcs at gmail dot com 2009-07-22 12:10 ---
(In reply to comment #129)
> I am a bit wondering if this bug is also for the case (a < b) && (b < a) ==
> true. Is it?
i guess so, see:
#include
#include
#define axiom_order(a,b) !(a &l
13 matches
Mail list logo
