From: Gabor Loki <loki@gcc.gnu.org>
To: David Daney <ddaney@avtrex.com>
Cc: Ian Lance Taylor <iant@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, testsuit] Add tests for PR33009
Date: Tue, 11 Mar 2008 09:51:00 -0000 [thread overview]
Message-ID: <47D65602.30001@gcc.gnu.org> (raw)
In-Reply-To: <47D61E22.8060907@avtrex.com>
David Daney wrote:
>>> * gcc.c-torture/compile/pr11832.c: Check -frtl-abstract-sequences.
>>> * gcc.c-torture/compile/pr33009.c: Likewise.
>>>
> These tests are failing on almost all targets except i686 and x86_64.
>
> Should we just xfail them, or is someone likely to fix rtl-factoring?
Maybe, but I am working on this topic.
More info and a possible fix can be found at PR33642.
> On mips the failure is in compute_init_costs where the result of
> make_jump_insn_raw doesn't match any insns so computing its length
> ICEs. I have not looked an any other targets.
Thanks your report.
As I see on mips-elf, the last patch from PR33642 fixed this problem.
-- Gabor Loki
next prev parent reply other threads:[~2008-03-11 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 13:38 Gabor Loki
2008-03-05 2:19 ` Ian Lance Taylor
2008-03-11 5:53 ` David Daney
2008-03-11 9:51 ` Gabor Loki [this message]
2008-03-07 19:50 ` David Daney
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=47D65602.30001@gcc.gnu.org \
--to=loki@gcc.gnu.org \
--cc=ddaney@avtrex.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.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).