public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos_Reis <gdosreis@sophia.inria.fr>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: Joe Buck <jbuck@synopsys.com>, gcc@gcc.gnu.org
Subject: Re: GCC-3.2.2 pre-release
Date: Wed, 29 Jan 2003 16:25:00 -0000	[thread overview]
Message-ID: <15927.55487.10260.788260@gauvain.inria.fr> (raw)
In-Reply-To: <200301291333.46841.ebotcazou@libertysurf.fr>

| > HP has a number of failures.  I see lots of failures for weak symbols that
| > aren't in the following report (from John David Anglin).  Perhaps a
| > different binutils version is being used?  Other than those, the failures
| > seem similar to what we had before.
| 
| Is the following bug a known problem, or... ? Because I think it comes close 
| to being a show stopper: 
| http://gcc.gnu.org/ml/gcc-bugs/2003-01/msg01706.html
| 
| However, gcc 3.2 and gcc 3.2.1 segfault too according to my preliminary 
| tests.

While a serious problem, if it^[OB were already present in 3.2.1 then it
does not qualify as regression or a showstopper.  That does not mean I
would not welcome a fix. 

-- Gaby

  reply	other threads:[~2003-01-29 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 13:12 Gabriel Dos_Reis
2003-01-28 19:20 ` Joe Buck
2003-01-28 19:58   ` Gabriel Dos Reis
2003-01-29  6:17 ` Joe Buck
2003-01-29  7:17   ` Gabriel Dos_Reis
2003-01-29  7:27     ` Joe Buck
2003-01-29 15:11   ` Eric Botcazou
2003-01-29 16:25     ` Gabriel Dos_Reis [this message]
2003-01-29 19:20       ` GCC-3.2.2 pre-release [and PR 9493] Joe Buck
2003-01-29 19:33         ` Gabriel Dos Reis
2003-01-29 21:49           ` Eric Botcazou
2003-01-29 22:50             ` Joe Buck
2003-01-29 22:53               ` Jan Hubicka
2003-01-30  0:08               ` Eric Botcazou
2003-01-28 21:11 GCC-3.2.2 pre-release Ulrich Weigand
2003-01-28 22:00 ` Gabriel Dos_Reis

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=15927.55487.10260.788260@gauvain.inria.fr \
    --to=gdosreis@sophia.inria.fr \
    --cc=ebotcazou@libertysurf.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.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).