public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jason@redhat.com,
	nobody@gcc.gnu.org
Subject: Re: middle-end/6950: gcc 3.0.4 miscompiles cppexp.c
Date: Tue, 03 Dec 2002 14:50:00 -0000	[thread overview]
Message-ID: <20021203225019.32057.qmail@sources.redhat.com> (raw)

Synopsis: gcc 3.0.4 miscompiles cppexp.c

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Tue Dec  3 14:50:17 2002
State-Changed-Why:
    Jason, this was a bug report against 3.0.4, that you thought
    would be worth while fixing for 3.0.5. However, you note that
    it was in the trunk back then. Can you say what is the status
    for this, i.e. whether it should be closed or not?
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6950


             reply	other threads:[~2002-12-03 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 14:50 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04  6:26 bangerth
2002-12-03 22:46 Jason Merrill
2002-06-06 16:56 jason

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=20021203225019.32057.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=nobody@gcc.gnu.org \
    /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).