public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gcc@gcc.gnu.org
Cc: mark@codesourcery.com, jbuck@synopsys.com, gdr@integrable-solutions.net
Subject: Re: What are the chances of another release from gcc-3_2-branch?
Date: Sat, 28 Dec 2002 03:47:00 -0000	[thread overview]
Message-ID: <200212280009.gBS09Q25002783@hiauly1.hia.nrc.ca> (raw)

> 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 a fix for parisc-linux that I would like to backport from 3.3.
It's not a regression, but 3.3 or later won't bootstrap with 3.2 because
of continued code growth in expr.c.  The change is small and the impact
is limited to the pa.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

             reply	other threads:[~2002-12-28  0:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28  3:47 John David Anglin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-27 23:58 Michael Elizabeth Chastain
2002-12-20  9:02 Volker Reichelt
2002-12-19 15:23 Michael Elizabeth Chastain
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-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
2002-12-27 13:21     ` Gabriel Dos Reis
2002-12-27 12:46 ` Gerald Pfeifer

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=200212280009.gBS09Q25002783@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=jbuck@synopsys.com \
    --cc=mark@codesourcery.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).