public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philip Blundell <Philip.Blundell@pobox.com>
To: Manfred Hollstein <manfred@s-direktnet.de>
Cc: law@cygnus.com, rms@gnu.org, Manfred.Hollstein@ks.sel.alcatel.de,
	oliva@dcc.unicamp.br, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: New problems with gcc-2.8.0 based code - NOW FIXED!
Date: Tue, 30 Dec 1997 11:33:00 -0000	[thread overview]
Message-ID: <E0xn5mO-00044A-00@paddington.london.uk.eu.org> (raw)
In-Reply-To: <199712301444.PAA00543@saturn.s-direktnet.de>

>  Dec 30 13:58:50 saturn kernel: Call Trace: [<c011b96d>] [<c011b99d>] [<c011c
>14c>] [<c0109f1a>]  

Can you run this through the ksymoops decoder to get a meaningful backtrace 
(with function names)?

>And so on - a lot of kernel Oops's follow.  I really don't know, who's
>to blame?!?!  Looking at Linux's `mm/slab.c' where the `kmem_free:..."
>messages result from, doesn't really help, as there is _NO_ loop! BUT,

More likely it's the function that calls the SLAB code that is to blame.  If 
you find out what that is and compile it with -S -funroll-all-loops, that 
might be the way forward.

>Does  anybody know  an   e-mail address whom    we can  forward  these
>questions?

linux-kernel@vger.rutgers.edu is probably your best bet.

p.



  parent reply	other threads:[~1997-12-30 11:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-10 12:02 cannot bootstrap neither gcc-2.8.0-971206 nor egcs-971207 on sparc-sun-sunos4.1.3 Alexandre Oliva
1997-12-10 23:09 ` Manfred.Hollstein
1997-12-11  3:32   ` Paul Eggert
1997-12-11  1:51     ` Manfred.Hollstein
1997-12-22 12:06   ` Jeffrey A Law
1997-12-22 22:04     ` Alexandre Oliva
1997-12-26  8:11     ` New problems with gcc-2.8.0 based code [was: Re: cannot bootstrap neither gcc-2.8.0-971206 nor egcs-971207 on sparc-sun-sunos4.1.3 ] Manfred Hollstein
1997-12-27 12:13       ` New problems with gcc-2.8.0 based code - NOW FIXED! Manfred Hollstein
1997-12-28 23:23         ` Richard Stallman
1997-12-29  7:48           ` Jeffrey A Law
1997-12-29 11:17             ` Manfred Hollstein
1997-12-29 10:20               ` Jeffrey A Law
1997-12-30  8:57                 ` Manfred Hollstein
1997-12-30  9:47                   ` Andi Kleen
1998-01-01 10:02                     ` Manfred Hollstein
1997-12-30 11:33                   ` Philip Blundell [this message]
1997-12-30 13:17                   ` Paul Koning
1997-12-29 11:08           ` Manfred Hollstein
     [not found] <199712302041.MAA25118@atrus.synopsys.com>
1997-12-30 13:45 ` Toon Moene
     [not found] <9712301949.AA01218@vlsi1.ultra.nyu.edu>
1997-12-30 13:52 ` Paul Koning
1997-12-30 12:27   ` Linus Torvalds
     [not found] <9712302109.AA01369@vlsi1.ultra.nyu.edu>
1997-12-30 14:41 ` Paul Koning
1997-12-30 23:05   ` Richard Stallman
     [not found] <9712302324.AA01798@vlsi1.ultra.nyu.edu>
1997-12-30 16:39 ` Paul Koning
     [not found] <E0xnN2N-0005UN-00@paddington.london.uk.eu.org>
     [not found] ` <199801030231.DAA25241@mail.macqel.be>
1998-01-05 10:13   ` Paul Koning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E0xn5mO-00044A-00@paddington.london.uk.eu.org \
    --to=philip.blundell@pobox.com \
    --cc=Manfred.Hollstein@ks.sel.alcatel.de \
    --cc=egcs@cygnus.com \
    --cc=gcc2@cygnus.com \
    --cc=law@cygnus.com \
    --cc=manfred@s-direktnet.de \
    --cc=oliva@dcc.unicamp.br \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).