public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/18034] GCC 3.4.2/GNAT bootstrap problem Date: Sat, 16 Oct 2004 15:01:00 -0000 [thread overview] Message-ID: <20041016150130.7980.qmail@sourceware.org> (raw) In-Reply-To: <20041016144902.18034.franke@euro-telematik.de> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-16 15:01 ------- Try looking into PR 6552 and PR 6669. Those two might tell you what the problem is. It might be stage1 is being miscompile which miscompiles stage2 which causes this problem. -- What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal Component|pending |target Keywords| |build, wrong-code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18034
next prev parent reply other threads:[~2004-10-16 15:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-16 14:49 [Bug pending/18034] New: " gcc-bugzilla at gcc dot gnu dot org 2004-10-16 15:01 ` pinskia at gcc dot gnu dot org [this message] 2004-10-26 19:02 ` [Bug target/18034] " rsandifo at gcc dot gnu dot org 2004-11-27 17:25 ` franke at euro-telematik dot de 2005-04-05 21:35 ` echristo at redhat dot com
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=20041016150130.7980.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: linkBe 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).