public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65243] [5 Regression] lto1 ICE (segfault) on powerpc64le-linux-gnu
Date: Mon, 02 Mar 2015 12:12:00 -0000	[thread overview]
Message-ID: <bug-65243-4-fqqhNgrr2g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65243-4@http.gcc.gnu.org/bugzilla/>

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

Matthias Klose <doko at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> ---
export COLLECT_GCC=/usr/bin/powerpc64le-linux-gnu-g++
export COLLECT_GCC_OPTIONS="'-c' '-fexceptions' '-fmath-errno' '-fsigned-zeros'
'-ftrapping-math' '-fno-trapv' '-fno-openmp' '-fno-openacc' '-msecure-plt'
'-mtune=power8' '-mcpu=power7' '-O3' '-O2' '-O3' '-v' '-save-temps' '-g' '-O3'
'-fstack-protector-strong' '-Werror=format-security' '-D' '_FORTIFY_SOURCE=2'
'-fPIE' '-pie' '-shared-libgcc' '-mtune=power8' '-mcpu=power7' '-dumpdir' './'
'-dumpbase' 'apt-cacher-ng.ltrans17' '-fltrans' '-o'
'apt-cacher-ng.ltrans17.ltrans.o' '-shared-libgcc'"
gdb --args  /usr/lib/gcc/powerpc64le-linux-gnu/5/lto1 -quiet -dumpdir ./
-dumpbase apt-cacher-ng.ltrans17 -msecure-plt -mtune=power8 -mcpu=power7
-mtune=power8 -mcpu=power7 -auxbase-strip apt-cacher-ng.ltrans17.ltrans.o -g
-O3 -O2 -O3 -O3 -Werror=format-security -version -fexceptions -fmath-errno
-fsigned-zeros -ftrapping-math -fno-trapv -fno-openmp -fno-openacc
-fstack-protector-strong -fPIE -fltrans apt-cacher-ng.ltrans17.o -o
apt-cacher-ng.ltrans17.s

Program received signal SIGSEGV, Segmentation fault.
0x0000000010c53690 in htab_hash_string ()
(gdb) bt
#0  0x0000000010c53690 in htab_hash_string ()
#1  0x000000001026a1d8 in lookup_external_ref(hash_table<external_ref_hasher,
xcallocator, false>*, die_struct*) ()
#2  0x000000001026a2d8 in optimize_external_refs_1(die_struct*,
hash_table<external_ref_hasher, xcallocator, false>*) ()
#3  0x000000001026a894 in optimize_external_refs(die_struct*) ()
#4  0x000000001026abf4 in output_comp_unit(die_struct*, int) ()
#5  0x000000001028d5cc in dwarf2out_finish(char const*) ()
#6  0x00000000105ca938 in compile_file() ()
#7  0x0000000010141374 in toplev::main(int, char**) ()
#8  0x0000000010141d78 in main ()


  parent reply	other threads:[~2015-03-02 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 18:26 [Bug lto/65243] New: " doko at gcc dot gnu.org
2015-03-02  8:44 ` [Bug lto/65243] " rguenth at gcc dot gnu.org
2015-03-02 12:12 ` doko at gcc dot gnu.org [this message]
2015-03-02 12:13 ` doko at gcc dot gnu.org
2015-03-06  2:35 ` msebor at gcc dot gnu.org
2015-03-06 19:07 ` law at redhat dot com
2015-03-09  1:46 ` hubicka at gcc dot gnu.org
2015-03-18  9:59 ` dcb314 at hotmail dot com
2015-03-18 13:20 ` rguenth at gcc dot gnu.org
2015-03-31 13:04 ` rguenth 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-65243-4-fqqhNgrr2g@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).