From: Christophe Lyon <christophe.lyon@linaro.org>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] patch to deal with insn scratches in global RA
Date: Thu, 5 Nov 2020 09:53:30 +0100 [thread overview]
Message-ID: <CAKdteOaicm_Jj0SA9cVGK3qM1UDUMTUSw8mZdnui6oJxtX1F2g@mail.gmail.com> (raw)
In-Reply-To: <660fc448-1e24-df69-8bce-ffccdcd420e7@redhat.com>
On Mon, 2 Nov 2020 at 23:01, Vladimir Makarov <vmakarov@redhat.com> wrote:
>
>
> On 2020-11-02 4:30 p.m., Vladimir Makarov via Gcc-patches wrote:
> >
> > On 2020-11-02 3:12 p.m., Christophe Lyon wrote:
> >>
> >> Hi,
> >>
> >> This patch causes ICEs on arm (eg arm-none-linux-gnueabi)
> >> gcc.c-torture/compile/sync-3.c -O1 (internal compiler error)
> >> gcc.c-torture/compile/sync-3.c -O2 (internal compiler error)
> >> gcc.c-torture/compile/sync-3.c -O2 -flto -fno-use-linker-plugin
> >> -flto-partition=none (internal compiler error)
> >> gcc.c-torture/compile/sync-3.c -O2 -flto -fuse-linker-plugin
> >> -fno-fat-lto-objects (internal compiler error)
> >> gcc.c-torture/compile/sync-3.c -O3 -g (internal compiler error)
> >> gcc.c-torture/compile/sync-3.c -Os (internal compiler error)
> >>
> >> gcc.log says:
> >> FAIL: gcc.c-torture/compile/sync-3.c -O1 (internal compiler error)
> >> PASS: gcc.c-torture/compile/sync-3.c -O1 (test for warnings, line )
> >> FAIL: gcc.c-torture/compile/sync-3.c -O1 (test for excess errors)
> >> Excess errors:
> >> during RTL pass: ira
> >> /gcc/testsuite/gcc.c-torture/compile/sync-3.c:85:1: internal compiler
> >> error: Segmentation fault
> >> 0xcf8b1f crash_signal
> >> /gcc/toplev.c:330
> >> 0xaeb0a0 fix_reg_equiv_init
> >> /gcc/ira.c:2671
> >> 0xaf2113 find_moveable_pseudos
> >> /gcc/ira.c:4874
> >> 0xaf48e8 ira
> >> /gcc/ira.c:5533
> >> 0xaf48e8 execute
> >> /gcc/ira.c:5861
> >
> >
> > Thank you for sending this info. I reproduced the crash with
> > x86-64-arm cross-compiler although it is absent on native arm
> > environment. I will have a fix tomorrow.
> >
> >
> I've fixed it.
>
Thanks, I confirm I no longer see this error.
Christophe
prev parent reply other threads:[~2020-11-05 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 19:11 Vladimir Makarov
2020-11-02 20:12 ` Christophe Lyon
2020-11-02 21:30 ` Vladimir Makarov
2020-11-02 22:01 ` Vladimir Makarov
2020-11-05 8:53 ` Christophe Lyon [this message]
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=CAKdteOaicm_Jj0SA9cVGK3qM1UDUMTUSw8mZdnui6oJxtX1F2g@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@redhat.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).