public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: Leo.van.den.Berg@bergtegels.nl, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: middle-end/7256: <synopsis of the problem (one line)>
Date: Tue, 03 Dec 2002 14:56:00 -0000	[thread overview]
Message-ID: <20021203225649.6694.qmail@sources.redhat.com> (raw)

Synopsis: <synopsis of the problem (one line)>

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Tue Dec  3 14:56:47 2002
State-Changed-Why:
    Hi Leo,
    regarding your bug report: the attachment unfortunately only
    contains some assembler code, but not the program input
    (in preprocessed form). Do you still have it? If so, 
    please send it to us so that we can add it to the bug data
    base and eventually fix the problem.
    
    Thanks
      Wolfgang

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


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 14:56 bangerth [this message]
2002-12-06  6:50 bangerth
2002-12-06  6:56 Wolfgang Bangerth

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=20021203225649.6694.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=Leo.van.den.Berg@bergtegels.nl \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --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).