public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Joe Buck <jbuck@synopsys.com>
Cc: mark@codesourcery.com (Mark Mitchell),
	phil@jaj.com (Phil Edwards),
	mec@shout.net (Michael Elizabeth Chastain),
	gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: What are the chances of another release from gcc-3_2-branch?
Date: Thu, 19 Dec 2002 15:16:00 -0000	[thread overview]
Message-ID: <200212192201.36952.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <200212191930.gBJJUnT19630@piper.synopsys.com>

> If we are going to do it, I would suggest freezing what we have (unless
> there's a very good argument for one or two more fixes), do a prerelease
> tarball, get some testing of that and ship.

I have one: we still have regressions from the 3.2 release regarding loops 
compiled with -O2 -funroll-loops on K6 (PR opt/8599) and powerpc. The patch 
is awaiting review and testing on powerpc here:
http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00787.html
http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00875.html

-- 
Eric Botcazou

  reply	other threads:[~2002-12-19 21:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 21:46 Michael Elizabeth Chastain
2002-12-19  0:15 ` Phil Edwards
2002-12-19 11:31   ` Mark Mitchell
2002-12-19 13:19     ` Joe Buck
2002-12-19 15:16       ` Eric Botcazou [this message]
2002-12-27 13:21     ` Gabriel Dos Reis
2002-12-27 12:46 ` Gerald Pfeifer
2002-12-19 13:15 Kaveh R. Ghazi
2002-12-19 15:25 ` Tom Tromey
2002-12-19 22:13   ` Kaveh R. Ghazi
2002-12-19 15:23 Michael Elizabeth Chastain
2002-12-20  9:02 Volker Reichelt
2002-12-27 23:58 Michael Elizabeth Chastain
2002-12-28  3:47 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=200212192201.36952.ebotcazou@libertysurf.fr \
    --to=ebotcazou@libertysurf.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    --cc=mark@codesourcery.com \
    --cc=mec@shout.net \
    --cc=phil@jaj.com \
    /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).