From: Richard Henderson <rth@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Fwd: C6X fails to build in FSF mainline
Date: Thu, 18 Aug 2011 15:16:00 -0000 [thread overview]
Message-ID: <4E4D2CCC.7040106@redhat.com> (raw)
In-Reply-To: <CA+=Sn1k-SFi_wJ5QgGvEeaZrhgTwiGCAmzi+PoLWJFX2E4ZH=A@mail.gmail.com>
On 08/17/2011 06:45 PM, Andrew Pinski wrote:
> gcc/libgcc2.c: In function ‘__gnu_mulsc3’:
> gcc/libgcc2.c:1928:1: internal compiler error: in scan_trace, at
> dwarf2cfi.c:2433
> Please submit a full bug report,
>
> I assume that it is because the C6X has more than one delay slot ?
Ug. I knew c6x has more than 1 delay slot (indeed, 5).
But I'd hoped that they were not annulled.
r~
next prev parent reply other threads:[~2011-08-18 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3zkj9o8o3.fsf@redhat.com>
2011-08-18 1:46 ` Andrew Pinski
2011-08-18 15:16 ` Richard Henderson [this message]
2011-08-18 17:16 ` Richard Henderson
2011-08-22 18:04 ` Bernd Schmidt
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=4E4D2CCC.7040106@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@gmail.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).