public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: prj@po.cwru.edu (Paul Jarc)
Cc: gcc@gcc.gnu.org
Subject: Re: Update: status of high-priority GNATS bugs
Date: Wed, 23 Oct 2002 19:22:00 -0000	[thread overview]
Message-ID: <200210232118.g9NLIBD28171@piper.synopsys.com> (raw)
In-Reply-To: <m3of9kevbm.fsf@multivac.cwru.edu> from "Paul Jarc" at Oct 23, 2002 04:47:19 PM


> PR 8146 seems to me to be a regression from 2.95.3.  It might be just
> a problem in my (rather unusual) environment, though - has anyone
> tried to reproduce it?  (FWIW, I can reproduce it with stock gcc 3.2,
> but not with the patched version Red Hat distributes with 8.0.)

I suspect that almost all Red Hat's patches are in 3.2.1-pre as well.
Could you test the 3.2 CVS branch or a recent 3.2-branch snapshot?


  reply	other threads:[~2002-10-23 21:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 10:05 Reichelt
2002-10-23 10:05 ` Paolo Carlini
2002-10-23 18:16 ` Paul Jarc
2002-10-23 19:22   ` Joe Buck [this message]
2002-10-23 23:11     ` Janis Johnson
2002-10-24 12:34     ` Paul Jarc
2002-10-24 12:41       ` Jakub Jelinek
2002-10-24 15:48         ` Paul Jarc
2002-10-24 16:45           ` Janis Johnson
2002-10-25  4:21         ` Paul Jarc
2002-10-25  7:06           ` Janis Johnson
2002-10-25  7:45             ` Paul Jarc
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23  2:27 Joe Buck
2002-10-23  2:30 ` David Edelsohn
2002-10-23 10:59   ` Joe Buck
2002-10-23 14:06     ` David Edelsohn
2002-10-24  9:17       ` Mark Mitchell
2002-10-23  2:57 ` Zack Weinberg
2002-10-23  4:36 ` Kaveh R. Ghazi
2002-10-23 10:12 ` Robert Lipe
2002-10-23 12:04   ` Richard Henderson
2002-10-23 15:46     ` Robert Lipe

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=200210232118.g9NLIBD28171@piper.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=prj@po.cwru.edu \
    /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).