From: Christophe Lyon <christophe.lyon@linaro.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Dominique Dhumieres <dominiq@lps.ens.fr>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Guenther <richard.guenther@gmail.com>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH 7/7] Plug ipa-prop escape analysis into gimple_call_arg_flags
Date: Mon, 26 May 2014 09:29:00 -0000 [thread overview]
Message-ID: <CAKdteOaFE+ToF9yfwXE=gXDkgt8ORb8CCZ87ncKhd8Od4cLjSA@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1kh4_fWbJa+d3UYEKbZ18v7aNFnzdJ5U_bq99APsVtCrA@mail.gmail.com>
On my side, I can see that r210901 breaks AArch64 compiler build:
gcc/config/aarch64/aarch64.c: In function ‘void
aarch64_elf_asm_named_section(const char*, unsigned int, tree_node*)’:
gcc/config/aarch64/aarch64.c:8136: error: ‘decl_comdat_group’ was not
declared in this scope
Christophe.
On 26 May 2014 11:16, Andrew Pinski <pinskia@gmail.com> wrote:
> On Mon, May 26, 2014 at 1:59 AM, Dominique Dhumieres <dominiq@lps.ens.fr> wrote:
>> r210901 breaks bootstrap on targets not supporting strnlen, e.g., darwin10.
>>
>> ../../_clean/gcc/lto-cgraph.c:976:68: error: 'strnlen' was not declared in this scope
>
> strnlen should be declared in include/libiberty.h if there is no
> declaration as libiberty support is already there. That should be a
> simple fix.
>
> Thanks,
> Andrew Pinski
>
>>
>> libgfortran/configure defines HAVE_STRNLEN on targets supporting it.
>>
>> The same revision also breaks the test g++.dg/tls/diag-1.C
>>
>> /opt/gcc/work/gcc/testsuite/g++.dg/tls/diag-1.C:31:1: internal compiler error: in symtab_get_node, at cgraph.h:1021
>>
>> TIA,
>>
>> Dominique
next prev parent reply other threads:[~2014-05-26 9:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 9:00 Dominique Dhumieres
2014-05-26 9:16 ` Andrew Pinski
2014-05-26 9:29 ` Christophe Lyon [this message]
2014-05-26 16:32 ` Jan Hubicka
2014-05-28 7:26 ` Thomas Schwinge
2014-05-28 21:55 ` Jan Hubicka
2014-06-03 9:56 ` Thomas Schwinge
2014-06-10 6:48 ` Commit policy? " Thomas Schwinge
2014-06-10 6:54 ` Andrew Pinski
2014-06-10 9:07 ` Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2014-05-21 13:31 [PATCH 0/7] ipa-prop escape analysis Martin Jambor
2014-05-21 13:31 ` [PATCH 7/7] Plug ipa-prop escape analysis into gimple_call_arg_flags Martin Jambor
2014-05-21 14:27 ` Richard Biener
2014-05-22 12:49 ` Martin Jambor
2014-05-22 13:34 ` Richard Biener
2014-05-22 15:24 ` Jan Hubicka
2014-05-22 15:36 ` Richard Biener
2014-05-22 18:11 ` Jan Hubicka
2014-05-23 10:03 ` Richard Biener
2014-05-23 22:29 ` Jan Hubicka
2014-05-24 7:39 ` Jan Hubicka
2014-05-26 13:03 ` Rainer Orth
2014-05-27 17:51 ` Jan Hubicka
2014-05-27 18:16 ` Rainer Orth
2014-05-26 1:01 ` Jan Hubicka
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='CAKdteOaFE+ToF9yfwXE=gXDkgt8ORb8CCZ87ncKhd8Od4cLjSA@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=dominiq@lps.ens.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.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).