public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jiwang at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64669] [5 Regression] aarch64-linux profiledbootstrap failure
Date: Mon, 19 Jan 2015 22:53:00 -0000	[thread overview]
Message-ID: <bug-64669-4-pv2H0ILfjp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64669-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64669

--- Comment #4 from Jiong Wang <jiwang at gcc dot gnu.org> ---
haven't enable go front end,

../gcc/configure --enable-languages=c,c++,fortran --disable-libsanitizer
--enable-checking=release --disable-werror 


with make -j16 profiledbootstrap, I got several 

../../../gcc/libgcc/libgcc2.c:858:1: internal compiler error: Segmentation
fault

and then the following final errors during stage2, will do further
investigation tomorrow.

tall-after-patch/aarch64-unknown-linux-gnu/bin/
-B/home/jiowan01/COMMUNITY/install-after-patch/aarch64-unknown-linux-gnu/lib/
-isystem
/home/jiowan01/COMMUNITY/install-after-patch/aarch64-unknown-linux-gnu/include
-isystem
/home/jiowan01/COMMUNITY/install-after-patch/aarch64-unknown-linux-gnu/sys-include
 -g -O2 -O2  -g -O2 -DIN_GCC    -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition 
-isystem ./include   -fPIC -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector   -fPIC -I. -I. -I../.././gcc -I../../../gcc/libgcc
-I../../../gcc/libgcc/. -I../../../gcc/libgcc/../gcc
-I../../../gcc/libgcc/../include  -DHAVE_CC_TLS  -o _clrsbdi2.o -MT _clrsbdi2.o
-MD -MP -MF _clrsbdi2.dep -DL_clrsbdi2 -c ../../../gcc/libgcc/libgcc2.c
-fvisibility=hidden -DHIDE_EXPORTS
0x645377 crash_signal
        ../../gcc/gcc/toplev.c:372
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[3]: *** [_popcountdi2.o] Error 1
make[3]: *** Waiting for unfinished jobs....
0x645377 crash_signal
        ../../gcc/gcc/toplev.c:372
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[3]: *** [_popcountsi2.o] Error 1
make[3]: Leaving directory
`/home/jiowan01/COMMUNITY/build-after-patch/aarch64-unknown-linux-gnu/libgcc'
make[2]: *** [all-stagefeedback-target-libgcc] Error 2
make[2]: Leaving directory `/home/jiowan01/COMMUNITY/build-after-patch'
make[1]: *** [stagefeedback-bubble] Error 2
make[1]: Leaving directory `/home/jiowan01/COMMUNITY/build-after-patch'
make: *** [profiledbootstrap] Error 2
~


  parent reply	other threads:[~2015-01-19 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-64669-4@http.gcc.gnu.org/bugzilla/>
2015-01-19 13:16 ` jakub at gcc dot gnu.org
2015-01-19 22:09 ` rth at gcc dot gnu.org
2015-01-19 22:53 ` jiwang at gcc dot gnu.org [this message]
2015-01-20 18:06 ` jiwang at gcc dot gnu.org
2015-01-20 18:10 ` jiwang at gcc dot gnu.org
2015-01-20 19:03 ` rth at gcc dot gnu.org
2015-01-20 19:15 ` pinskia at gcc dot gnu.org
2015-01-20 19:40 ` rth at gcc dot gnu.org
2015-01-21  9:33 ` jakub at gcc dot gnu.org
2015-01-21 14:16 ` jiwang at gcc dot gnu.org
2015-01-21 15:48 ` rth at gcc dot gnu.org
2015-01-21 15:50 ` rth at gcc dot gnu.org

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=bug-64669-4-pv2H0ILfjp@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).