This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Kernel 2.1.117 OOPS w/egcs
- To: Dax Kelson <dkelson at inconnect dot com>
- Subject: Re: Kernel 2.1.117 OOPS w/egcs
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Fri, 21 Aug 1998 23:40:39 -0600
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
> ---------- Forwarded message ----------
> Date: Fri, 21 Aug 1998 06:01:13 -0700 (PDT)
> From: Linus Torvalds <torvalds@transmeta.com>
> To: rbarnett <rbarnett@scf-fs.usc.edu>
> Cc: Kernel Mailing List <linux-kernel@vger.rutgers.edu>
> Subject: Re: Kernel 2.1.117 OOPS bug report
>
>
>
> On Thu, 20 Aug 1998, rbarnett wrote:
> >
> > I'm using egcs-2.90.27 980315 (egcs-1.0.2 release) with binutils
> > 2.8.1.0.23.
> >
> > Running gdb 4.17 on vmlinux (2.1.117) displays the following output:
> >
> > (gdb) x/10i __switch_to
> > 0xc01088d0 <__switch_to>: pushl %esi
> > 0xc01088d1 <__switch_to+1>: pushl %ebx
> > 0xc01088d2 <__switch_to+2>: movl 0xc(%esp,1),%ebx
> > 0xc01088d6 <__switch_to+6>: movl 0x10(%esp,1),%ecx
>
> Ok, egcs for some reason refuses to do the fastcall thing.
>
> > Your interpretation? Shall I reinstall GNU gcc and abandon egcs?
>
> I wonder. The above certainly implies that at least your particular
> version of egcs cannot compile the current kernels, but I don't know why.
> Before abandoning egcs you might want to talk to some egcs people to see
> whether there is some simple way to make egcs do the right thing.
There's no information in this message which helps me determine what
the right thing to do is or what we are doing wrong. Also no testcase.
I can't do anything with such bug reports.
jeff