All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually
Date: Tue, 19 Dec 2006 19:02:39 -0600	[thread overview]
Message-ID: <20061220010239.GM5506@austin.ibm.com> (raw)
In-Reply-To: <1166575984.19254.101.camel@localhost.localdomain>

On Wed, Dec 20, 2006 at 11:53:04AM +1100, Benjamin Herrenschmidt wrote:
> On Tue, 2006-12-19 at 18:46 -0600, Linas Vepstas wrote:
> > Hi Ben, 
> > 
> > Per xchat, here's the update. I'm guessing I'm using a broken
> > compiler, as per chain of evidence below ... 
> > 
> > I noticed that linux-2.6.20-rc1-git6 crashes on power4
> > in SMP mode:
> 
> Have you tried a different gcc to confirm ?

tommorrow .. 

  reply	other threads:[~2006-12-20  1:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  0:46 Bad gcc-4.1.0 leads to Power4 crashes... and power5 too, actually Linas Vepstas
2006-12-20  0:53 ` Benjamin Herrenschmidt
2006-12-20  1:02   ` Linas Vepstas [this message]
2006-12-20  1:46 ` Peter Bergner
2006-12-20 21:19   ` Linas Vepstas
2006-12-20 21:28     ` Benjamin Herrenschmidt
2006-12-20 23:03       ` Mutex debug lock failure [was " Linas Vepstas
2006-12-20 23:03         ` Linas Vepstas
2006-12-20 23:09         ` Benjamin Herrenschmidt
2006-12-20 23:09           ` Benjamin Herrenschmidt
2006-12-20 23:46           ` Linas Vepstas
2006-12-20 23:46             ` Linas Vepstas
2006-12-21  0:36             ` Anton Blanchard
2006-12-21  0:36               ` Anton Blanchard
2006-12-21  1:03               ` Linas Vepstas
2006-12-21  1:03                 ` Linas Vepstas
2006-12-21 14:41                 ` Ingo Molnar
2006-12-21 14:41                   ` Ingo Molnar
2006-12-21 21:12                   ` Linas Vepstas
2006-12-21 21:12                     ` Linas Vepstas
2006-12-23  6:28     ` Alan Modra

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=20061220010239.GM5506@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.