public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jojelino at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/47584] [4.6 regression] internal compiler error: sigsegv in libcpp/line-map.c:285
Date: Wed, 02 Feb 2011 19:33:00 -0000 [thread overview]
Message-ID: <bug-47584-4-Xc6guvdnVS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47584-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47584
gee <jojelino at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Host|i686-pc-mingw32 |i686-pc-cygwin
--- Comment #6 from gee <jojelino at gmail dot com> 2011-02-02 19:33:39 UTC ---
i686-pc-mingw32-gcc -v
Using built-in specs.
COLLECT_GCC=i686-pc-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-mingw32/4.6.0/lto-wrapper.exe
Target: i686-pc-mingw32
Configured with: ./configure --config-cache --prefix=/usr
--enable-win32-registry --enable-threads=win32 --enable-languages=c,c++,lto
--with-win32-nlsapi=unicode --enable-tls --disable-bootstrap
--target=i686-pc-mingw32 --enable-shared --enable-interpreter
--disable-sjlj-exceptions --enable-gomp
Thread model: win32
gcc version 4.6.0 20110202 (experimental) (GCC)
i'm sorry for this.
next prev parent reply other threads:[~2011-02-02 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 7:06 [Bug driver/47584] New: " jojelino at gmail dot com
2011-02-02 7:07 ` [Bug driver/47584] " jojelino at gmail dot com
2011-02-02 7:23 ` jojelino at gmail dot com
2011-02-02 12:11 ` [Bug target/47584] " rguenth at gcc dot gnu.org
2011-02-02 18:34 ` [Bug pch/47584] " pinskia at gcc dot gnu.org
2011-02-02 18:48 ` ktietz at gcc dot gnu.org
2011-02-02 19:33 ` jojelino at gmail dot com [this message]
2011-02-04 13:45 ` jakub at gcc dot gnu.org
2011-02-08 15:04 ` rguenth at gcc dot gnu.org
2011-03-07 10:36 ` [Bug pch/47584] " 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-47584-4-Xc6guvdnVS@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).