--- Comment #7 from patriciak784-gccmainling at yahoo dot de 2008-09-04
09:50 ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > ... a self compiled gcc 4.3.1 ...
> > >
> > > Scary ;)
> > >
> > What did you expec
--- Comment #6 from pinskia at gcc dot gnu dot org 2008-09-03 21:14 ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > ... a self compiled gcc 4.3.1 ...
> >
> > Scary ;)
> >
> What did you expect, Paolo?
He was joking as we all compile GCC by us
--- Comment #5 from patriciak784-gccmainling at yahoo dot de 2008-09-03
12:21 ---
(In reply to comment #4)
> (In reply to comment #3)
> > ... a self compiled gcc 4.3.1 ...
>
> Scary ;)
>
What did you expect, Paolo?
Well, I just compiled gcc-4_3-branch @ rev 137894 and the resulting g
--- Comment #4 from paolo dot carlini at oracle dot com 2008-09-03 11:06
---
(In reply to comment #3)
> ... a self compiled gcc 4.3.1 ...
Scary ;)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37331
--- Comment #3 from patriciak784-gccmainling at yahoo dot de 2008-09-03
10:46 ---
(In reply to comment #2)
> Most likely the same issue as PR 37215.
>
I don't know. This problem is totally strange...
I checked my linux machine and some debian gcc 4.3.1-xx works correctly and
also a se
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-09-02 20:50 ---
Most likely the same issue as PR 37215.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37331
--- Comment #1 from patriciak784-gccmainling at yahoo dot de 2008-09-02
14:37 ---
Please be aware that compiling /dev/null is used in glibc to produce empty
object files!
So it seems not to be a crazy thing to do...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37331