On Fri, Jan 05, 2001 at 11:24:15PM -0800, Ron Farrer wrote:
I haven't looked at this (yet?), but I would guess it to be more bugs
in gcc 2.95 we are using. If you look at the gcc 2.96 changelog you'll
see there are quite a few bug fixes, a lot of them on Alpha. We've
been plauged with bad
On Sat, Jan 06, 2001 at 03:18:29PM -0500, Jim Crilly wrote:
Just wanted to note I see a similar problem compiling the DAC960 driver in
the 2.4 (2.2.X one works fine) kernel, with -O2 gcc segfaults, with -O0 it
works.
Sorry for not giving more information but my Alpha's at work right now
On Sun, Jan 07, 2001 at 06:18:29PM +0100, Matthias Klose wrote:
Just wanted to note I see a similar problem compiling the DAC960 driver in
the 2.4 (2.2.X one works fine) kernel, with -O2 gcc segfaults, with -O0 it
works.
Sorry for not giving more information but my Alpha's at
I just installed and tried that compiler and it didn't work either, but
gave a real error, or atleast what looks like one, instead of just
segfaulting. This is what I got:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.0/include -Wall -Wstrict-prototypes -
O2 -fomit-frame-pointer -fno-strict-aliasing
On Fri 05 Jan 2001, Ron Farrer wrote:
Anthony Towns (aj@azure.humbug.org.au) wrote:
Like the subject says; if I build ifupdown (0.6.4-1) on alpha with -O2
it breaks, if I build it with -O0, it's fine. With -O2, trying to trace
what's going on with gdb doesn't seem to work (it jumps all
Please check with a gcc-2.95.3 prerelease compiled by Chris
(http://master.debian.org/~doko/alpha) or with the test release
currently in incoming.
Current gcc snapshots (2.97) can be found in experimental (currently in
incoming).
Jim Crilly writes:
Anthony Towns (aj@azure.humbug.org.au)
Anthony Towns (aj@azure.humbug.org.au) wrote:
Like the subject says; if I build ifupdown (0.6.4-1) on alpha with -O2
it breaks, if I build it with -O0, it's fine. With -O2, trying to trace
what's going on with gdb doesn't seem to work (it jumps all over the
place, fairly meaninglessly).
In
Anthony Towns (aj@azure.humbug.org.au) wrote:
Like the subject says; if I build ifupdown (0.6.4-1) on alpha with -O2
it breaks, if I build it with -O0, it's fine. With -O2, trying to trace
what's going on with gdb doesn't seem to work (it jumps all over the
place, fairly meaninglessly).
(Please Cc me, I'm not on the debian-alpha list)
Hello world,
Like the subject says; if I build ifupdown (0.6.4-1) on alpha with -O2
it breaks, if I build it with -O0, it's fine. With -O2, trying to trace
what's going on with gdb doesn't seem to work (it jumps all over the
place, fairly
9 matches
Mail list logo