public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.nixman at autistici dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/60244] New: GCC-trunk rev.207809, Segmentation fault when executing ".../xgcc -dumpspecs"
Date: Mon, 17 Feb 2014 14:55:00 -0000	[thread overview]
Message-ID: <bug-60244-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60244

            Bug ID: 60244
           Summary: GCC-trunk rev.207809, Segmentation fault when
                    executing ".../xgcc -dumpspecs"
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: i.nixman at autistici dot org

configure options:
../../../src/gcc-trunk/configure \
--host=i686-w64-mingw32 \
--build=i686-w64-mingw32 \
--target=i686-w64-mingw32 \
--prefix=/mingw32 \
--with-sysroot=/d/mingwtrunk/i686-trunk-posix-dwarf-rt_v4/mingw32 \
--with-gxx-include-dir=/mingw32/i686-w64-mingw32/include/c++ \
--enable-shared \
--enable-static \
--disable-multilib \
--enable-languages=c,c++,lto \
--enable-libstdcxx-time=yes \
--enable-threads=posix \
--enable-libgomp \
--enable-lto \
--enable-graphite \
--enable-checking=release \
--enable-fully-dynamic-string \
--enable-version-specific-runtime-libs \
--disable-sjlj-exceptions \
--with-dwarf2 \
--disable-isl-version-check \
--disable-cloog-version-check \
--disable-libstdcxx-pch \
--disable-libstdcxx-debug \
--enable-bootstrap \
--disable-rpath \
--disable-win32-registry \
--disable-nls \
--disable-werror \
--disable-symvers \
--with-gnu-as \
--with-gnu-ld \
--with-arch=i686 \
--with-tune=generic \
--with-libiconv \
--with-system-zlib \
--enable-cloog-backend=isl


Previously, I've successfully built GCC-trunk rev.205009 with the same options.

Also, I've successfully built rev.207809 as x86_64-posix-sjlj &
i686-posix-sjlj. That is I suspect that the reason is that the problem occurred
with the build using DWARF.


             reply	other threads:[~2014-02-17 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 14:55 i.nixman at autistici dot org [this message]
2014-03-17  8:01 ` [Bug bootstrap/60244] " ktietz at gcc dot gnu.org
2014-03-17 17:56 ` i.nixman at autistici dot org
2014-05-10  5:09 ` halo9pan03 at gmail dot com
2014-05-14  1:08 ` halo9pan03 at gmail dot com
2015-02-09 18:50 ` pinskia at gcc dot gnu.org
2015-02-10 17:13 ` ktietz 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-60244-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).