public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/64102] New: ARM bootstrap fails with segfault with -mapcs in BOOT_CFLAGS
Date: Fri, 28 Nov 2014 13:55:00 -0000	[thread overview]
Message-ID: <bug-64102-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64102
           Summary: ARM bootstrap fails with segfault with -mapcs in
                    BOOT_CFLAGS
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ktkachov at gcc dot gnu.org

I'm seeing a bootstrap segfault in stage2 on arm-none-linux-gnueabihf when
given BOOT_CFLAGS="-O2 -mapcs":

$BUILD/./gcc/xgcc -B$BUILD/./gcc/ -B$BUILD/armv7l-unknown-linux-gnueabihf/bin/
-B$BUILD/armv7l-unknown-linux-gnueabihf/lib/ -isystem
$BUILD/armv7l-unknown-linux-gnueabihf/include -isystem
$BUILD/armv7l-unknown-linux-gnueabihf/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 -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector   -fPIC -fno-inline -I. -I. -I../.././gcc -I$SRC/libgcc
-I$SRC/libgcc/. -I$SRC/libgcc/../gcc -I$SRC/libgcc/../include  -DHAVE_CC_TLS 
-o _eprintf.o -MT _eprintf.o -MD -MP -MF _eprintf.dep -DL_eprintf -c
$SRC/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS

$SRC/libgcc/libgcc2.c: In function '__eprintf':
$SRC/libgcc/libgcc2.c:2114:3: internal compiler error: Segmentation fault
   fprintf (stderr, string, expression, line, filename);
   ^
0x69c0cf crash_signal
        $SRC/gcc/toplev.c:359
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.
(kyrtka01@pdtl-cb1)~/builds/gcc-bootstrap-apcs-clean/

This is based on r218090 with configuration:
--with-float=hard --with-cpu=cortex-a15 --with-mode=arm --with-fpu=neon-vfpv4
--enable-languages=c,c++,fortran

Bootstrap without -mapcs works fine.
I don't know if this is a regression, didn't try released compilers.

Can someone please confirm this?


             reply	other threads:[~2014-11-28 13:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 13:55 ktkachov at gcc dot gnu.org [this message]
2014-11-28 14:01 ` [Bug bootstrap/64102] " ktkachov at gcc dot gnu.org
2014-11-28 14:06 ` ktkachov at gcc dot gnu.org
2014-12-01 11:30 ` ktkachov at gcc dot gnu.org
2014-12-01 13:50 ` ktkachov at gcc dot gnu.org
2014-12-09  9:18 ` ktkachov at gcc dot gnu.org
2015-01-15 13:28 ` ramana 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-64102-4@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).