From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH GCC8][01/33]Handle TRUNCATE between tieable modes in rtx_cost
Date: Wed, 03 May 2017 09:00:00 -0000 [thread overview]
Message-ID: <CAHFci2_9qJH+fCHRrHS9iBUHukVs2khzKVb2zpKDqCwkZzz=Ow@mail.gmail.com> (raw)
In-Reply-To: <4598428.28LrkgqxJG@polaris>
On Wed, May 3, 2017 at 7:17 AM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> 2017-04-11 Bin Cheng <bin.cheng@arm.com>
>>
>> * rtlanal.c (rtx_cost): Handle TRUNCATE between tieable modes.
>
> This breaks bootstrap with RTL checking:
>
> /home/eric/build/gcc/native/./gcc/xgcc -B/home/eric/build/gcc/native/./gcc/ -
> nostdinc -x c /dev/null -S -o /dev/null -fself-
> test=/home/eric/svn/gcc/gcc/testsuite/selftests
> cc1: internal compiler error: RTL check: expected code 'subreg', have
> 'truncate' in rtx_cost, at rtlanal.c:4169
> 0xbae338 rtl_check_failed_code1(rtx_def const*, rtx_code, char const*, int,
> char const*)
> /home/eric/svn/gcc/gcc/rtl.c:829
> 0xbbc9b4 rtx_cost(rtx_def*, machine_mode, rtx_code, int, bool)
> /home/eric/svn/gcc/gcc/rtlanal.c:4169
> 0x8517e6 set_src_cost
> /home/eric/svn/gcc/gcc/rtl.h:2685
> 0x8517e6 init_expmed_one_conv
> /home/eric/svn/gcc/gcc/expmed.c:142
> 0x8517e6 init_expmed_one_mode
> /home/eric/svn/gcc/gcc/expmed.c:209
> 0x853fb2 init_expmed()
> /home/eric/svn/gcc/gcc/expmed.c:270
> 0xc45974 backend_init_target
> /home/eric/svn/gcc/gcc/toplev.c:1665
> 0xc45974 initialize_rtl()
>
Sorry for disturbing, I will revert this if can't fix today.
Thanks,
bin
> --
> Eric Botcazou
next prev parent reply other threads:[~2017-05-03 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 10:38 Bin Cheng
2017-04-24 21:23 ` Jeff Law
2017-05-03 7:33 ` Eric Botcazou
2017-05-03 9:00 ` Bin.Cheng [this message]
2017-05-03 10:07 ` Bin.Cheng
2017-05-03 10:12 ` Kyrill Tkachov
2017-05-03 10:12 ` Bin.Cheng
2017-05-03 14:38 ` Christophe Lyon
2017-05-10 14:38 ` Bin.Cheng
2017-05-11 15:02 ` Christophe Lyon
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='CAHFci2_9qJH+fCHRrHS9iBUHukVs2khzKVb2zpKDqCwkZzz=Ow@mail.gmail.com' \
--to=amker.cheng@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@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: 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).