public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/40742] GCC (for Microblaze) reports internal compiler error Date: Tue, 14 Jul 2009 09:26:00 -0000 [thread overview] Message-ID: <20090714092610.17955.qmail@sourceware.org> (raw) In-Reply-To: <bug-40742-17947@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from steven at gcc dot gnu dot org 2009-07-14 09:26 ------- Microblaze is not an FSF GCC version. Please report this bug to the distributor of mb-gcc (Google says this is http://www.petalogix.com/resources/downloads/mb-gcc). and kindly request them to adjust the bug-reporting URL also. -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Component|target |c Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40742
prev parent reply other threads:[~2009-07-14 9:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-14 8:53 [Bug c/40742] New: " klaus-christian dot saalfeld at sma dot de 2009-07-14 9:24 ` [Bug target/40742] " rguenth at gcc dot gnu dot org 2009-07-14 9:26 ` steven at gcc dot gnu dot org [this message]
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=20090714092610.17955.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).