public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wileypob@yahoo.com
To: gcc-gnats@gcc.gnu.org
Cc: joel.sherrill@OARcorp.com
Subject: target/9248: compiling C++ file from ACE causes ICE on m68k-rtems target
Date: Thu, 09 Jan 2003 16:06:00 -0000 [thread overview]
Message-ID: <20030109160446.12544.qmail@sources.redhat.com> (raw)
>Number: 9248
>Category: target
>Synopsis: compiling C++ file from ACE causes ICE on m68k-rtems target
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Thu Jan 09 08:06:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Tim Housel
>Release: 3.2.1 (with rtems patch ftp://ftp.oarcorp.com/pub/rtems/cd-working/tools/gcc3.2.1newlib1.10.0-4/source/gcc-3.2.1-rtems-20021209.diff)
>Organization:
>Environment:
target m68k-rtems (elf)
host i686-cygwin (running on Windows 2000)
$ m68k-rtems-g++ -v
Reading specs from /cygdrive/c/m68k-rtems-tools/lib/gcc-lib/m68k-rtems/3.2.1/specs
Configured with: ../gcc-3.2.1/configure --target=m68k-rtems --with-gnu-as --with-gnu-ld --with-newlib --verbose --enable-threads --prefix=/cygdrive/c/m68k-rtems-tools --enable-languages=c,c++
Thread model: rtems
gcc version 3.2.1
>Description:
When compiling a C++ file, I received an ICE for a couple of the m68k targets (-mcpu32 and -m68040).
>How-To-Repeat:
m68k-rtems-g++ -mcpu32 -c Stats.ii
m68k-rtems-g++ -m68040 -c Stats.ii
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-01-09 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 16:06 wileypob [this message]
2003-01-09 20:08 joel
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=20030109160446.12544.qmail@sources.redhat.com \
--to=wileypob@yahoo.com \
--cc=gcc-gnats@gcc.gnu.org \
--cc=joel.sherrill@OARcorp.com \
/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).