public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mlangejans at aos-hagenuk dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16641] fr30-elf-gcc compiler error when building newlib-1.12.0
Date: Tue, 20 Jul 2004 15:22:00 -0000 [thread overview]
Message-ID: <20040720152206.30083.qmail@sourceware.org> (raw)
In-Reply-To: <20040720110911.16641.mlangejans@aos-hagenuk.com>
------- Additional Comments From mlangejans at aos-hagenuk dot com 2004-07-20 15:22 -------
(In reply to comment #1)
> Can you read http://gcc.gnu.org/bugs.html and add the preprocessed source?
Hello Andrew,
I read the note at the entrance,... sorry for barging in ;-).
I'm not sure this is the right destination for the bug, since I use the mingw
version of GCC 3.4.1,...
The preprocessed file and options used to build this GCC are added as attachments.
Hope it can be fixed.
Thanks,
Marco
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Ever Confirmed| |1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16641
next prev parent reply other threads:[~2004-07-20 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 11:09 [Bug c/16641] New: " mlangejans at aos-hagenuk dot com
2004-07-20 14:03 ` [Bug target/16641] " pinskia at gcc dot gnu dot org
2004-07-20 14:30 ` pinskia at gcc dot gnu dot org
2004-07-20 15:22 ` mlangejans at aos-hagenuk dot com [this message]
[not found] <bug-16641-8950@http.gcc.gnu.org/bugzilla/>
2006-04-23 17:25 ` sayle at gcc dot gnu dot org
2006-04-23 21:19 ` roger at eyesopen dot com
[not found] <bug-16641-4@http.gcc.gnu.org/bugzilla/>
2021-09-19 9:37 ` pinskia at gcc dot gnu.org
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=20040720152206.30083.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).