public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk,
	ml4cwq@sina.com.cn, nobody@gcc.gnu.org
Subject: Re: c/2487: arm-linux-gcc
Date: Fri, 22 Jun 2001 05:16:00 -0000	[thread overview]
Message-ID: <20010622121630.25732.qmail@sourceware.cygnus.com> (raw)

Synopsis: arm-linux-gcc

State-Changed-From-To: open->feedback
State-Changed-By: jsm28
State-Changed-When: Fri Jun 22 05:16:30 2001
State-Changed-Why:
    You didn't provide preprocessed source as the instructions
    at the URL the compiler gave asked you to.  Does the problem
    still occur with GCC 3.0?  If so, please provide
    preprocessed source.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2487&database=gcc


             reply	other threads:[~2001-06-22  5:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22  5:16 jsm28 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-20 14:22 jsm28
2001-04-05  0:56 ml4cwq

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=20010622121630.25732.qmail@sourceware.cygnus.com \
    --to=jsm28@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    --cc=ml4cwq@sina.com.cn \
    --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).