From: Dave Korn <dave.korn.cygwin@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Andrew Haley <aph@redhat.com>,
Richard Guenther <richard.guenther@gmail.com>,
Richard Guenther <rguenther@suse.de>,
Tobias Burnus <burnus@net-b.de>,
Gerald Pfeifer <gerald@pfeifer.com>,
Mark Mitchell <mark@codesourcery.com>, GCC <gcc@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: End of GCC 4.6 Stage 1: October 27, 2010
Date: Tue, 21 Sep 2010 17:27:00 -0000 [thread overview]
Message-ID: <4C98B286.3090201@gmail.com> (raw)
In-Reply-To: <AANLkTik7meeXwdo6SxYnFmSGUbgBtxVyaNtncYDXQUeE@mail.gmail.com>
On 21/09/2010 02:51, NightStrike wrote:
> The toolchain is broken once again here:
>
> x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../../../build/mingw/mingw-w64-crt
> -m32 -I../../../build/mingw/mingw-w64-crt/include -D_CRTBLD -I/tmp/build/root/x
> 86_64-w64-mingw32/include -pipe -std=gnu99 -Wall -Wextra -Wformat -Wstrict-ali
> asing -Wshadow -Wpacked -Winline -Wimplicit-function-declaration -Wmissing-noret
> urn -Wmissing-prototypes -g -O2 -MT math/lib32_libmingwex_a-sf_erf.o -MD -MP -MF
> math/.deps/lib32_libmingwex_a-sf_erf.Tpo -c -o math/lib32_libmingwex_a-sf_erf.o
> `test -f 'math/sf_erf.c' || echo '../../../build/mingw/mingw-w64-crt/'`math/sf_
> erf.c
> ../../../build/mingw/mingw-w64-crt/math/sf_erf.c: In function `__trunc_float_wor
> d.isra.0':
> ../../../build/mingw/mingw-w64-crt/math/sf_erf.c:268:1: internal compiler error:
> tree check: expected var_decl, have debug_expr_decl in const_value_known_p, at
> varpool.c:375
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45738
cheers,
DaveK
next prev parent reply other threads:[~2010-09-21 13:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 22:55 Mark Mitchell
2010-09-05 4:23 ` NightStrike
2010-09-05 18:03 ` Mark Mitchell
2010-09-05 18:23 ` NightStrike
2010-09-05 18:29 ` Mark Mitchell
2010-09-05 18:35 ` NightStrike
2010-09-05 18:40 ` Mark Mitchell
2010-09-05 22:10 ` Gerald Pfeifer
2010-09-05 22:18 ` Tobias Burnus
2010-09-06 9:22 ` Richard Guenther
2010-09-06 16:19 ` NightStrike
2010-09-06 16:21 ` Richard Guenther
2010-09-06 16:33 ` Tim Prince
2010-09-06 17:18 ` NightStrike
2010-09-06 17:24 ` Andrew Haley
2010-09-06 17:32 ` NightStrike
2010-09-20 23:23 ` NightStrike
2010-09-21 10:01 ` Jonathan Wakely
2010-09-21 15:09 ` NightStrike
2010-09-21 17:27 ` Dave Korn [this message]
2010-09-23 22:09 ` NightStrike
2010-10-08 15:56 ` NightStrike
2010-10-08 16:06 ` Jonathan Wakely
2010-10-08 16:10 ` Kai Tietz
2010-10-08 16:54 ` NightStrike
2010-10-08 18:04 ` Jonathan Wakely
2010-10-08 18:11 ` NightStrike
2010-10-09 1:40 ` Dave Korn
2011-02-24 17:05 ` NightStrike
2010-10-08 21:09 ` Richard Guenther
2010-10-08 21:14 ` NightStrike
2010-10-09 0:42 ` Richard Guenther
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=4C98B286.3090201@gmail.com \
--to=dave.korn.cygwin@gmail.com \
--cc=aph@redhat.com \
--cc=burnus@net-b.de \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jwakely.gcc@gmail.com \
--cc=mark@codesourcery.com \
--cc=nightstrike@gmail.com \
--cc=rguenther@suse.de \
--cc=richard.guenther@gmail.com \
/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).