--- Comment #12 from cnstar9988 at gmail dot com 2007-07-26 08:20 ---
I want the warning.
but why the warning is glibc's bug?
because memset(x,19,0), is buggy code.
I need the warning.
--
cnstar9988 at gmail dot com changed:
What|Removed |Added
--
--- Comment #11 from cnstar9988 at gmail dot com 2007-07-26 08:13 ---
Created an attachment (id=13981)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13981&action=view)
(64bit)gcc -m32 -O3 -Wall test.c -save-temps
(64bit)gcc -m32 -O3 -Wall test.c -save-temps
In this platform, it'
--- Comment #10 from pinskia at gcc dot gnu dot org 2007-07-26 08:10
---
This is a bug in glibc version you are using, the warning is comming from the
expansion of a #define. Looking at the expanded version, I see that glibc is
violating C aliasing rules anyways so the code might not
--- Comment #9 from cnstar9988 at gmail dot com 2007-07-26 08:02 ---
Created an attachment (id=13980)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13980&action=view)
file
gcc -m32 -O3 -Wall test.c -save-temps
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32887
--- Comment #8 from pinskia at gcc dot gnu dot org 2007-07-26 07:50 ---
It might be, can you attach the preprocessed source? Which you can find by
adding -save-temps and it will be either end in .i or .ii. The difference in
glibc versions could be cause different warnings to show up in
--- Comment #7 from cnstar9988 at gmail dot com 2007-07-26 07:45 ---
test.c:14: warning: statement with no effect
So I think it is gcc warning
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32887
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-07-26 07:42 ---
> can gernerate warning on gcc-4.2.1 on x86
What is the warning? Because I am not seeing it.
It might be that glibc is doing the warning. Can you paste the warning you are
getting?
--
http://gcc.gnu.org/bugzil
--- Comment #5 from cnstar9988 at gmail dot com 2007-07-26 02:29 ---
Why the behavior on both platform is not the same?
same code, same release of GCC.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32887
--- Comment #4 from cnstar9988 at gmail dot com 2007-07-25 09:13 ---
I download GCC from ftp.gnu.org, 4.2.1 release.
gcc -O3 -Wall test.c
can gernerate warning on gcc-4.2.1 on x86
but no warning on gcc-4.2.1/x64. even -m32 or -m64.
I only think the behavior on both platform is the sam
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-07-25 09:09 ---
(In reply to comment #2)
> why gcc show warnings on x86.
I am saying this does not warn in a normal FSF GCC release. So what warning do
you expect? A warning for a zero sized memset? Well the FSF GCC does not war
--- Comment #2 from cnstar9988 at gmail dot com 2007-07-25 02:49 ---
why gcc show warnings on x86.
not show warnings on x64?
Bug?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32887
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-25 02:43 ---
What is the warning that you are expecting? We don't warn at all for memset
with a zero size.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
12 matches
Mail list logo
