public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Nathanael Nerode" <neroden@fastmail.fm>
Cc: <gcc@gcc.gnu.org>
Subject: Re: disable ivopts by default for 4.0?
Date: Sat, 27 Nov 2004 21:58:00 -0000	[thread overview]
Message-ID: <0a7d01c4d4c2$ae5f94a0$db422597@bagio> (raw)
In-Reply-To: <20041127182347.GA22823@fastmail.fm>

Nathanael Nerode <neroden@fastmail.fm> wrote:

> Disabling it by default (rendering the ivopts bugs non-regressions)
> would cut the regression list down to a reasonable and more
> manageable length.  Would it generate any new regressions?  I doubt
> it.

Only if you prove that it does not generate any codegen regression from older
versions of GCC, on any major platform. I do not think that starting disabling
problematic passes in GCC is a good shortcut to get the release out.

> It seems to be the cause of a lot of the remaining 4.0 regressions,
> including many of the wrong-code regressions.

I would debate this as well. There are around 200 regressions now, 80 of which
are already 3.4 or 3.3 regressions so they are not surely related of ivopts. Of
the other 120, I would be surprised if more than 15 are caused by ivopts. You
can setup a ivopts meta-bug, link all the regressions ivopts causes to this
meta-bug, and get back to us with some numbers.

Giovanni Bajo

  reply	other threads:[~2004-11-27 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27 20:48 Nathanael Nerode
2004-11-27 21:58 ` Giovanni Bajo [this message]
2004-11-28 19:17 ` Zdenek Dvorak
2004-11-28 23:08 Nathanael Nerode

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='0a7d01c4d4c2$ae5f94a0$db422597@bagio' \
    --to=giovannibajo@libero.it \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@fastmail.fm \
    /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).