From: Jeff Law <jlaw@ventanamicro.com>
To: Xi Ruoyao <xry111@xry111.site>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jivan Hakobyan <jivanhakobyan9@gmail.com>
Subject: Re: [RFA] New pass for sign/zero extension elimination
Date: Sun, 19 Nov 2023 20:48:46 -0700 [thread overview]
Message-ID: <c3ca84e1-01d0-44f7-bd5b-e8c71c105512@ventanamicro.com> (raw)
In-Reply-To: <5e54ada2f2a818e6ed375044a07895469bec0010.camel@xry111.site>
On 11/19/23 20:32, Xi Ruoyao wrote:
> On Sun, 2023-11-19 at 19:52 -0700, Jeff Law wrote:
>
> /* snip */
>
>>
>>> Unfortunately, I get some ICE building stage 1 libgcc with this patch on
>>> loongarch64-linux-gnu:
>>>
>>> during RTL pass: ext_dce
>>> ../../../gcc/libgcc/libgcc2.c: In function ‘__absvdi2’:
>>> ../../../gcc/libgcc/libgcc2.c:224:1: internal compiler error: Segmentation fault
>>> 224 | }
>>> | ^
>>> 0x120baa477 crash_signal
>>> ../../gcc/gcc/toplev.cc:316
>>> 0x1216aeeb4 ext_dce_process_sets
>>> ../../gcc/gcc/ext-dce.cc:128
>>> 0x1216afbaf ext_dce_process_bb
>>> ../../gcc/gcc/ext-dce.cc:647
>>> 0x1216afbaf ext_dce
>>> ../../gcc/gcc/ext-dce.cc:802
>>> 0x1216afbaf execute
>>> ../../gcc/gcc/ext-dce.cc:868
>>> Please submit a full bug report, with preprocessed source (by using -freport-bug).
>>> Please include the complete backtrace with any bug report.
>>> See <https://gcc.gnu.org/bugs/> for instructions.
>> I think I know what's going on here.
>
> The gzip-compressed preprocessed file attached, in case you still need
> it.
Thanks. I'll double check with it in a bit. Basically there was a
late cleanup that could result in walking down the wrong part of a chunk
of RTL. My tester is about 30-60 minutes from being able to start a run
with the fix.
Jeff
next prev parent reply other threads:[~2023-11-20 3:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 0:47 Jeff Law
2023-11-20 1:22 ` Oleg Endo
2023-11-20 2:51 ` Jeff Law
2023-11-20 2:57 ` Oleg Endo
2023-11-20 2:23 ` Xi Ruoyao
2023-11-20 2:46 ` Jeff Law
2023-11-20 2:52 ` Jeff Law
2023-11-20 3:32 ` Xi Ruoyao
2023-11-20 3:48 ` Jeff Law [this message]
2023-11-20 18:26 ` Richard Sandiford
2023-11-22 17:59 ` Jeff Law
2023-11-27 20:15 ` Richard Sandiford
2023-11-20 18:56 ` Dimitar Dimitrov
2023-11-22 22:23 ` Jeff Law
2023-11-26 16:42 ` rep.dot.nop
2023-11-27 16:14 ` Jeff Law
2023-11-27 11:30 ` Andrew Stubbs
2023-11-27 16:16 ` Jeff Law
2023-12-01 1:08 ` Hans-Peter Nilsson
2023-12-01 15:09 ` Jeff Law
2023-12-01 16:17 ` Hans-Peter Nilsson
2023-11-27 17:36 Joern Rennecke
2023-11-27 17:57 ` Joern Rennecke
2023-11-27 20:03 ` Richard Sandiford
2023-11-27 20:18 ` Jeff Law
2023-11-28 13:36 ` Joern Rennecke
2023-11-28 14:09 ` Joern Rennecke
2023-11-30 17:33 ` Jeff Law
2023-11-28 13:13 ` Joern Rennecke
2023-11-28 5:50 ` Jeff Law
2023-11-27 18:19 Joern Rennecke
2023-11-28 5:51 ` Jeff Law
2023-11-29 17:37 Joern Rennecke
2023-11-29 19:13 ` Jivan Hakobyan
2023-11-30 15:37 ` Jeff Law
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=c3ca84e1-01d0-44f7-bd5b-e8c71c105512@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jivanhakobyan9@gmail.com \
--cc=xry111@xry111.site \
/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).