public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@porcupine.slc.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/7254: GCC Error target = MN10200 Date: Wed, 10 Jul 2002 11:06:00 -0000 [thread overview] Message-ID: <20020710180602.14181.qmail@sources.redhat.com> (raw) The following reply was made to PR other/7254; it has been noted by GNATS. From: Jeff Law <law@porcupine.slc.redhat.com> To: chilung@itri.org.tw Cc: gcc-gnats@gcc.gnu.org Subject: Re: other/7254: GCC Error target = MN10200 Date: Wed, 10 Jul 2002 12:08:20 -0600 In message <20020710061853.13108.qmail@sources.redhat.com>, chilung@itri.org.tw writes: > >>Number: 7254 >>Category: other >>Synopsis: GCC Error target = MN10200 >>Confidential: no >>Severity: serious >>Priority: medium >>Responsible: unassigned >>State: open >>Class: sw-bug >>Submitter-Id: net >>Arrival-Date: Tue Jul 09 23:26:00 PDT 2002 >>Closed-Date: >>Last-Modified: >>Originator: chilung@itri.org.tw >>Release: GCC 3.1 >>Organization: >>Environment: >Linux >>Description: >The GCC 3.1 Target = MN10200. Compiler the following > >==================== >void f() >{ >} >==================== > >A Compiler exception occcurs. Note that the mn102 port is currently scheduled to be removed in the next major release of GCC as it's currently unmaintained and believed to be unused. Are you planning to use the mn102 port for anything? If so, what? jeff
next reply other threads:[~2002-07-10 18:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-10 11:06 Jeff Law [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-10 7:43 giovannibajo 2003-02-19 14:24 bangerth 2003-02-19 13:46 Steven Bosscher 2002-07-10 17:26 Chilung Wang 2002-07-09 23:26 chilung
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=20020710180602.14181.qmail@sources.redhat.com \ --to=law@porcupine.slc.redhat.com \ --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: 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).