public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: "Alex Velenko" <Alex.Velenko@arm.com>,
	"Steve Ellcey" <sellcey@imgtec.com>,
	"Jack Howarth" <howarth.at.gcc@gmail.com>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>,
	"Martin Liška" <mliska@suse.cz>,
	"Jakub Jelinek" <jakub@redhat.com>,
	"James Greenhalgh" <james.greenhalgh@arm.com>
Subject: Re: ipa-icf::merge TLC
Date: Mon, 02 Mar 2015 22:04:00 -0000	[thread overview]
Message-ID: <CAKdteObRM_ShL7JT2fRPAAK69rws7FnRm+bkosJuRGjM83MyAw@mail.gmail.com> (raw)
In-Reply-To: <20150302202137.GB846@kam.mff.cuni.cz>

On 2 March 2015 at 21:21, Jan Hubicka <hubicka@ucw.cz> wrote:
>>
>>
>> On 01/03/15 16:47, Christophe Lyon wrote:
>> >On 27 February 2015 at 21:49, Jan Hubicka <hubicka@ucw.cz> wrote:
>> >>>
>> >>>../sysdeps/gnu/siglist.c:72:1: internal compiler error: in address_matters_p, at symtab.c:1908
>> >>>  versioned_symbol (libc, __new_sys_sigabbrev, sys_sigabbrev, GLIBC_2_3_3);
>> >>>  ^
>> >>>0x66a080 symtab_node::address_matters_p()
>> >>>         /scratch/sellcey/repos/bootstrap/src/gcc/gcc/symtab.c:1908
>> >>>0xe7cbe5 ipa_icf::sem_variable::merge(ipa_icf::sem_item*)
>> >>>         /scratch/sellcey/repos/bootstrap/src/gcc/gcc/ipa-icf.c:1443
>> >>
>> >>Indeed, the ipa-icf should not try to analyze aliases - just prove ekvialence of
>> >>definitions they are attached to.  It already does that for functions (bit by accident;
>> >>it gives up when there is no gimple body), but it does not do that for variables because
>> >>it gets into ctor_for_folding. For that reason it sometimes decides to try to make two
>> >>variable aliases alias of each other that is not a good idea, because of possible creation
>> >>of loops.
>> >>
>> >>I am just discussing with Martin the fix.
>> >>
>> >>Honza
>> >
>> >For the record, I have noticed similar errors on ARM and AArch64
>> >targets, when building glibc.
>> >
>> >Christophe.
>> >
>>
>> I confirm ARM and AArch64 failing to build with this patch:
>> chmod a-w /work/build-aarch64-none-linux-gnu/obj/glibc/stdio-common/errlist-compat.cT
>> 0x6b9100 symtab_node::address_matters_p()
>>       /work/src/gcc/gcc/symtab.c:1908
>> 0xedb4e5 ipa_icf::sem_variable::merge(ipa_icf::sem_item*)
>>       /work/src/gcc/gcc/ipa-icf.c:1723
>> 0xee03f9 ipa_icf::sem_item_optimizer::merge_classes(unsigned int)
>>       /work/src/gcc/gcc/ipa-icf.c:2955
>> 0xee6d31 ipa_icf::sem_item_optimizer::execute()
>>       /work/src/gcc/gcc/ipa-icf.c:2217
>> 0xee8df1 ipa_icf_driver
>>       /work/src/gcc/gcc/ipa-icf.c:3034
>> 0xee8df1 ipa_icf::pass_ipa_icf::execute(function*)
>>       /work/src/gcc/gcc/ipa-icf.c:3081
>
> I commited patch for the alias merging yesterda night, so it should be fixed
> now.  If it still fails, please fill in a PR with preprocessed testcase so I
> can reproduce it in a cross.
>

On my side, I saw builds complete again starting with r221090, I guess
that's the commit you are referring to?

Thanks,

Christophe.

> Honza
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> Please include the complete backtrace with any bug report.
>> See <http://gcc.gnu.org/bugs.html> for instructions.
>> make[2]: ***
>> [/work/build-aarch64-none-linux-gnu/obj/glibc/stdio-common/siglist.o]
>> Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> mv -f /work/build-aarch64-none-linux-gnu/obj/glibc/stdio-common/errlist-compat.cT /work/build-aarch64-none-linux-gnu/obj/glibc/stdio-common/errlist-compat.c
>>
>> Regards,
>> Alex

  reply	other threads:[~2015-03-02 22:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  9:03 Jan Hubicka
2015-02-25 13:10 ` Markus Trippelsdorf
2015-02-25 17:31   ` Jan Hubicka
2015-02-25 18:41     ` Martin Liška
2015-02-25 19:02       ` Markus Trippelsdorf
2015-02-26 16:46 ` Jack Howarth
2015-02-27  5:55   ` Jan Hubicka
2015-02-27 13:48     ` H.J. Lu
2015-02-27 18:04       ` Jan Hubicka
2015-02-27 18:39     ` Steve Ellcey
2015-02-27 18:56       ` Steve Ellcey
2015-02-27 20:00         ` Martin Liška
2015-02-27 21:16       ` Jan Hubicka
2015-03-01 16:47         ` Christophe Lyon
2015-03-02 19:01           ` Alex Velenko
2015-03-02 20:21             ` Jan Hubicka
2015-03-02 22:04               ` Christophe Lyon [this message]
2015-03-03 12:44                 ` Alex Velenko
2015-03-03 15:06                   ` Christophe Lyon
2015-03-03 20:01                     ` Jan Hubicka
2015-03-04  9:11                       ` Christophe Lyon
2015-02-28 16:38     ` James Greenhalgh
2015-02-28 18:15       ` Jan Hubicka
2015-03-04  9:38         ` James Greenhalgh
2015-03-06 16:09           ` [ARM testsuite obvious] Fixup atomic-comp-swap-release-acquire.c to not use ICF James Greenhalgh
2015-03-06 16:13             ` James Greenhalgh

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=CAKdteObRM_ShL7JT2fRPAAK69rws7FnRm+bkosJuRGjM83MyAw@mail.gmail.com \
    --to=christophe.lyon@linaro.org \
    --cc=Alex.Velenko@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=howarth.at.gcc@gmail.com \
    --cc=hubicka@ucw.cz \
    --cc=jakub@redhat.com \
    --cc=james.greenhalgh@arm.com \
    --cc=mliska@suse.cz \
    --cc=sellcey@imgtec.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).