public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Laurent GUERBY <laurent@guerby.net>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc <gcc@gcc.gnu.org>, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Annoucing regressions and bootstrap fail? (was: Bootstrap broken  on sparc-linux trunk between 145310:145425  because of new genattrtab.c  va_arg (p, HOST_WIDE_INT) warning)
Date: Sun, 05 Apr 2009 16:14:00 -0000	[thread overview]
Message-ID: <1238946634.10782.116.camel@localhost> (raw)
In-Reply-To: <6dc9ffc80904050825k5d73c881u94114888269f06fb@mail.gmail.com>

On Sun, 2009-04-05 at 08:25 -0700, H.J. Lu wrote:
> On Sun, Apr 5, 2009 at 2:25 AM, Laurent GUERBY <laurent@guerby.net> wrote:

> > I'm thinking of changing my auto tester to report a broken bootstrap
> > (the first time a bootstrap fails), is there a normalized way to
> > report such failures to gcc-testresults@ or gcc@?

> 
> I report it to gcc-regression@.

It's documented by http://gcc.gnu.org/lists.html as "read-only":

gcc-regression is a read-only moderate volume list where regression
results for the GCC compilers are posted.

So I thought one couldn't post to it.

If there's consensus that's the right place to send automatic regression
and bootstrap fail reports I'll do that then.

Laurent


  reply	other threads:[~2009-04-05 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05 15:25 Bootstrap broken on sparc-linux trunk between 145310:145425 because of new genattrtab.c va_arg (p, HOST_WIDE_INT) warning Laurent GUERBY
2009-04-05 15:49 ` H.J. Lu
2009-04-05 16:14   ` Laurent GUERBY [this message]
2009-09-13 22:49     ` Annoucing regressions and bootstrap fail? (was: Bootstrap broken on sparc-linux trunk between 145310:145425 because of new genattrtab.c va_arg (p, HOST_WIDE_INT) warning) Gerald Pfeifer
2009-04-08  1:11 ` Bootstrap broken on sparc-linux trunk between 145310:145425 because of new genattrtab.c va_arg (p, HOST_WIDE_INT) warning Joseph S. Myers

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=1238946634.10782.116.camel@localhost \
    --to=laurent@guerby.net \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=hjl.tools@gmail.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).