public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Regression fixes only
Date: Thu, 03 Sep 2009 13:09:00 -0000	[thread overview]
Message-ID: <4A9FC010.5030401@starynkevitch.net> (raw)
In-Reply-To: <alpine.LNX.2.00.0909031434460.28140@zhemvz.fhfr.qr>

Richard Guenther wrote:
> As we've got quite some build problems on some targets and we clashed
> with VTA, free-lang-data, expand and scheduler changes it's a good
> time to slush the trunk for a short time.
> 
> Thus, starting from now the trunk is in regression and documentation
> fixes only mode.

I hope that does not mean that gcc has switched mysteriously from stage 
1 to stage 3 (or even stage 2).

I am extremly interested in having the gengtype plugin patch accepted - 
that is the gengtype.[ch] part of
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00047.html

I would be very sad if I have to wait six months for it to go into the 
trunk (and as several people did notice, it is necessary for any plugins 
  needing GGC).

So Richard, can we understand that GCC is in regression and 
documentation fixes only mode for only a few days? Or did you decide a 
stage 1 end? [I hope you did not].

Regards.
-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

  reply	other threads:[~2009-09-03 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 12:37 Richard Guenther
2009-09-03 13:09 ` Basile STARYNKEVITCH [this message]
2009-09-03 13:16   ` Diego Novillo
2009-09-08  9:13 ` Trunk in regular stage1 again Richard Guenther

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=4A9FC010.5030401@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).