Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [bug] gcc-4.[23] miscompiling causing networking to bugger up
Date: Wed, 28 May 2008 19:41:10 -0400	[thread overview]
Message-ID: <20080528234110.GD30501@phobos.i.cabal.ca> (raw)
In-Reply-To: <119aab440805281637x722fd461n335a49aaa41c8a2c@mail.gmail.com>

On Wed, May 28, 2008 at 07:37:14PM -0400, Carlos O'Donell wrote:
> On Wed, May 28, 2008 at 7:00 PM, Kyle McMartin <kyle@mcmartin.ca> wrote:
> > Building the kernel without optimization is very tetchy... if you can
> > guess what passes to remove, I can try... one of the optimization
> > effects that must go is DCE though, otherwise we'll have undefined
> > references to things (ie: kmalloc_too_much in a switch that should have
> > been eliminated except the constant case.)
> 
> You *need* to build the kernel with -fno-dce and -fno-tree-dce?
> Are you working around another compiler bug?
> 
> Take a look at the attached scripts I use.
> 
> ./o2list.sh > o2list.txt
> ./permute-options.sh o2list.txt > run.sh
> chmod u+x
> run.sh
> 
> Normally I can simply run the results on a target and
> know which is good and which is bad. Unfortunately
> you have to link each into a kernel and try to boot.
> 

Other way around... we *need* dce (but apparnetly not on this file)
because of inline constructs like

	switch (sizeof(some constant)) {
	1:
		blah;
	default:
		some_undefined_reference();
	}

Ah well, anyway, it works built at -O0, and buggers up at -O1.

Want a copy of each of the .S?

  reply	other threads:[~2008-05-28 23:41 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 [this message]
2008-05-29  0:00           ` John David Anglin
2008-05-29  0:02             ` Kyle McMartin
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=20080528234110.GD30501@phobos.i.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=carlos@systemhalted.org \
    --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