From: Jan Hubicka <hubicka@ucw.cz>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: Backporting streaming and enum changes
Date: Fri, 14 Aug 2020 11:21:20 +0200 [thread overview]
Message-ID: <20200814092120.GE56176@kam.mff.cuni.cz> (raw)
In-Reply-To: <20200814091520.GD56176@kam.mff.cuni.cz>
> Hi,
> >
> > Since this was backported as r10-8623-g0d96c3424bbb5e5f994b78c8f65d8704d215be54,
>
> Yes, after discussion with Jakub on IRC.
> > I've noticed ICEs on arm and aarch64:
> > gcc.dg/pr34457-1.c (internal compiler error)
> > gcc.dg/torture/pr92088-1.c -O2 -flto -fno-use-linker-plugin
> > -flto-partition=none (internal compiler error)
> > gcc.dg/torture/pr92088-1.c -O2 -flto -fuse-linker-plugin
> > -fno-fat-lto-objects (internal compiler error)
> >
> > I can see:
> > Excess errors:
> > during IPA pass: cp
> > lto1: internal compiler error: in operator[], at vec.h:878
> > 0xa0a5d7 vec<lto_encoder_entry, va_heap, vl_embed>::operator[](unsigned int)
> > /gcc/vec.h:878
> > 0xa0a5d7 vec<lto_encoder_entry, va_heap, vl_ptr>::operator[](unsigned int)
> > /gcc/vec.h:1444
> > 0xa194d3 vec<lto_encoder_entry, va_heap, vl_ptr>::operator[](unsigned int)
> > /gcc/tree.h:3408
> > 0xa194d3 lto_symtab_encoder_deref
> > /gcc/lto-streamer.h:1173
> > 0xa194d3 ipa_prop_read_section
> > /gcc/ipa-prop.c:5060
> > 0xa194d3 ipa_prop_read_jump_functions()
> > /gcc/ipa-prop.c:5089
> > 0xb6ba71 ipa_read_summaries_1
> > /gcc/passes.c:2837
> > 0x6bc4b5 read_cgraph_and_symbols(unsigned int, char const**)
> > /gcc/lto/lto-common.c:2921
> > 0x69deb2 lto_main()
> > /gcc/lto/lto.c:625
> >
> > The tests pass on trunk.
>
> I will check this out. I seem to remember that we fixed the issue on
> mainline. It was extra zero byte streaming, I will dig it out.
Found it,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95362
I will backport the patch shortly. Sorry for the breakage - it is quite
impressive that we do not have non-trivial SCC streamed in the distro bootstrap.
Honza
>
> Honza
> >
> > Christophe
> > > Thanks,
> > > Richard.
> > >
> > > > Honza
> > > >
> > >
> > > --
> > > Richard Biener <rguenther@suse.de>
> > > SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg,
> > > Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2020-08-14 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 14:34 Jan Hubicka
2020-08-06 14:39 ` Richard Biener
2020-08-14 8:36 ` Christophe Lyon
2020-08-14 9:15 ` Jan Hubicka
2020-08-14 9:21 ` Jan Hubicka [this message]
2020-08-14 9:30 ` 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=20200814092120.GE56176@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).