From: Christophe Lyon <christophe.lyon@linaro.org>
To: Sebastian Pop <sebpop@gmail.com>
Cc: Teresa Johnson <tejohnson@google.com>, Jeff Law <law@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>, David Li <davidxl@google.com>
Subject: Re: [PATCH] Redesign jump threading profile updates
Date: Wed, 01 Oct 2014 15:25:00 -0000 [thread overview]
Message-ID: <CAKdteOYJ_Htoi8w=+1XLkTvk0zL+qQoWgNOUGJHcJcGmAe8_JQ@mail.gmail.com> (raw)
In-Reply-To: <20141001152256.GA24862@f1.c.bardezibar.internal>
On 1 October 2014 17:22, Sebastian Pop <sebpop@gmail.com> wrote:
> Christophe Lyon wrote:
>> Since this commit, I can see all my builds for arm*linux* and
>> aarch64*linux* fail while building glibc:
>>
>> /tmp/3496222_18.tmpdir/aci-gcc-fsf/builds/gcc-fsf-gccsrc/tools/bin/aarch64-none-linux-gnu-gcc
>> iso-2022-cn.c -c -std=gnu99 -fgnu89-inline -O2 -Wall -Win
>> line -Wundef -Wwrite-strings -fmerge-all-constants -frounding-math -g
>> -Wstrict-prototypes -fPIC -I../include
>> -I/tmp/3496222_18.tmpdir/aci-gcc-f
>> sf/builds/gcc-fsf-gccsrc/obj-aarch64-none-linux-gnu/glibc-1/iconvdata
>> -I/tmp/3496222_18.tmpdir/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-aarch64-none-linux
>> -gnu/glibc-1 -I../sysdeps/unix/sysv/linux/aarch64/nptl
>> -I../sysdeps/unix/sysv/linux/aarch64
>> -I../sysdeps/unix/sysv/linux/generic -I../sysdeps/unix/s
>> ysv/linux/wordsize-64 -I../nptl/sysdeps/unix/sysv/linux
>> -I../nptl/sysdeps/pthread -I../sysdeps/pthread
>> -I../sysdeps/unix/sysv/linux -I../sysdeps/gn
>> u -I../sysdeps/unix/inet -I../nptl/sysdeps/unix/sysv
>> -I../sysdeps/unix/sysv -I../nptl/sysdeps/unix -I../sysdeps/unix
>> -I../sysdeps/posix -I../sysd
>> eps/aarch64/fpu -I../sysdeps/aarch64/nptl -I../sysdeps/aarch64
>> -I../sysdeps/wordsize-64 -I../sysdeps/ieee754/ldbl-128
>> -I../sysdeps/ieee754/dbl-64/w
>> ordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32
>> -I../sysdeps/aarch64/soft-fp -I../sysdeps/ieee754
>> -I../sysdeps/generic -I../npt
>> l -I.. -I../libio -I. -nostdinc -isystem
>> /tmp/3496222_18.tmpdir/aci-gcc-fsf/builds/gcc-fsf-gccsrc/tools/lib/gcc/aarch64-none-linux-gnu/5.0.0/include
>> -i
>> system /tmp/3496222_18.tmpdir/aci-gcc-fsf/builds/gcc-fsf-gccsrc/tools/lib/gcc/aarch64-none-linux-gnu/5.0.0/include-fixed
>> -isystem /tmp/3496222_18.tmpdir
>> /aci-gcc-fsf/builds/gcc-fsf-gccsrc/sysroot-aarch64-none-linux-gnu/usr/include
>> -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -DSHARED
>> -DNOT_IN_libc -o
>> /tmp/3496222_18.tmpdir/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-aarch64-none-linux-gnu/glibc-1/iconvdata/iso-2022-cn.os
>> -MD -MP -MF /tmp/3
>> 496222_18.tmpdir/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-aarch64-none-linux-gnu/glibc-1/iconvdata/iso-2022-cn.os.dt
>> -MT /tmp/3496222_18.tmpdir/aci-gcc-fsf
>> /builds/gcc-fsf-gccsrc/obj-aarch64-none-linux-gnu/glibc-1/iconvdata/iso-2022-cn.os
>>
>> In file included from iso-2022-cn.c:407:0:
>> ../iconv/skeleton.c: In function 'gconv':
>> ../iconv/skeleton.c:800:1: internal compiler error: in
>> check_probability, at basic-block.h:959
>> 0xe4e2fb find_many_sub_basic_blocks(simple_bitmap_def*)
>> /tmp/3496222_18.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/basic-block.h:959
>> 0x6623f0 execute
>> /tmp/3496222_18.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/cfgexpand.c:5916
>> 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.
>>
>> Can you have a look?
>
> It would help if you could attach a preprocessed file.
>
I did it in a followup mail, but the list server rejected it because
it was too large.
I suppose Teresa did receive it though.
Not sure whether I can attach it in .xz format? Is this allowed?
Thanks
Christophe.
> Thanks,
> Sebastian
next prev parent reply other threads:[~2014-10-01 15:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 23:57 Teresa Johnson
2014-04-17 5:58 ` Jeff Law
2014-04-17 13:46 ` Teresa Johnson
2014-05-27 14:11 ` Teresa Johnson
2014-07-07 21:22 ` Teresa Johnson
2014-07-07 21:24 ` Jeff Law
2014-07-23 13:47 ` Jeff Law
2014-07-23 21:52 ` Teresa Johnson
2014-08-02 5:10 ` Teresa Johnson
2014-08-02 5:16 ` Andrew Pinski
2014-09-29 14:20 ` Teresa Johnson
2014-09-30 4:33 ` Jeff Law
2014-09-30 18:20 ` Teresa Johnson
2014-10-01 7:03 ` Christophe Lyon
2014-10-01 13:21 ` Teresa Johnson
2014-10-01 14:05 ` Teresa Johnson
2014-10-01 15:23 ` Sebastian Pop
2014-10-01 15:25 ` Christophe Lyon [this message]
2014-10-01 15:29 ` Teresa Johnson
2014-10-01 16:20 ` H.J. Lu
2014-10-01 16:23 ` Teresa Johnson
2014-10-01 20:05 ` Teresa Johnson
2014-10-01 22:46 ` Steve Ellcey
2014-10-02 5:02 ` Teresa Johnson
2014-10-02 15:44 ` Teresa Johnson
2014-10-02 15:45 ` Steve Ellcey
2014-10-02 16:01 ` Teresa Johnson
2014-10-01 23:09 ` Jan Hubicka
2014-10-02 5:07 ` Teresa Johnson
2014-10-02 18:34 ` Jeff Law
2014-10-28 16:01 ` Renlin Li
2014-10-01 15:36 ` Sebastian Pop
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='CAKdteOYJ_Htoi8w=+1XLkTvk0zL+qQoWgNOUGJHcJcGmAe8_JQ@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=sebpop@gmail.com \
--cc=tejohnson@google.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).