Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
	carlos@systemhalted.org, linux-parisc@vger.kernel.org
Subject: Re: [bug] gcc-4.[23] miscompiling causing networking to bugger up
Date: Wed, 28 May 2008 20:02:19 -0400	[thread overview]
Message-ID: <20080529000219.GE30501@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080529000059.9C6434E77@hiauly1.hia.nrc.ca>

On Wed, May 28, 2008 at 08:00:58PM -0400, John David Anglin wrote:
> > Ah well, anyway, it works built at -O0, and buggers up at -O1.
> > 
> > Want a copy of each of the .S?
> 
> I think it would be useful to know if this is still present in 4.3 branch
> head.  Unless we know which routine the problem is in, comparing .s files
> is tough.
> 
> I'm busy until just before the summit.
> 

I tried 4.4 from svn a few days (more like 2 weeks maybe) ago. Is that
recent enough or should I try 4.3-head as well (no problem to do.)

r, Kyle

  reply	other threads:[~2008-05-29  0:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 19:09 [bug] gcc-4.[23] miscompiling causing networking to bugger up Kyle McMartin
2008-05-28 20:00 ` Kyle McMartin
2008-05-28 22:55   ` Carlos O'Donell
2008-05-28 23:00     ` Kyle McMartin
2008-05-28 23:37       ` Carlos O'Donell
2008-05-28 23:41         ` Kyle McMartin
2008-05-29  0:00           ` John David Anglin
2008-05-29  0:02             ` Kyle McMartin [this message]
2008-05-29  0:07               ` Carlos O'Donell
2008-05-29  0:15                 ` Kyle McMartin
2008-05-31  4:10                 ` [bug] gcc-4.3 " Kyle McMartin
2008-05-31 10:58                   ` Matthew Wilcox
2008-06-01  1:37                     ` Grant Grundler
2008-05-31 14:43                   ` Carlos O'Donell
2008-05-29  1:11               ` [bug] gcc-4.[23] " John David Anglin

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=20080529000219.GE30501@phobos.i.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=carlos@systemhalted.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=linux-parisc@vger.kernel.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