public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "john dot spelis at 3dlabs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/16640] In function `__floattidf':, libgcc2.c:1292: internal compiler error: in expand_shift, at expmed.c:2111 Date: Tue, 20 Jul 2004 17:22:00 -0000 [thread overview] Message-ID: <20040720172239.14997.qmail@sourceware.org> (raw) In-Reply-To: <20040720100818.16640.john.spelis@3dlabs.com> ------- Additional Comments From john dot spelis at 3dlabs dot com 2004-07-20 17:22 ------- Andrew, I apologise, i'm new to Bugzilla and did not read your comment until posting my own. You guy's are hero's and Geniuses. Keep up the magnificent work. Best Regards. (In reply to comment #3) > Actually that means it is fixed and a bug in 3.0.x which is known and I thought was documented. > And it is: > From <http://gcc.gnu.org/install/specific.html>: > GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of the GNU compiler (especially > GCC 3.0.x versions), which lead to the miscompilation of the stage1 compiler and the subsequent > failure of the bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary stage, i.e. to > bootstrap that compiler with the base compiler and then use it to bootstrap the final compiler. (In reply to comment #3) > Actually that means it is fixed and a bug in 3.0.x which is known and I thought was documented. > And it is: > From <http://gcc.gnu.org/install/specific.html>: > GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of the GNU compiler (especially > GCC 3.0.x versions), which lead to the miscompilation of the stage1 compiler and the subsequent > failure of the bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary stage, i.e. to > bootstrap that compiler with the base compiler and then use it to bootstrap the final compiler. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16640
prev parent reply other threads:[~2004-07-20 17:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-20 10:09 [Bug c/16640] New: In function `__floattidf':, libgcc2.c:1292: internal compiler error: in expand_shift, at ex john dot spelis at 3dlabs dot com 2004-07-20 13:51 ` [Bug target/16640] In function `__floattidf':, libgcc2.c:1292: internal compiler error: in expand_shift, at expmed.c:2111 pinskia at gcc dot gnu dot org 2004-07-20 14:15 ` pinskia at gcc dot gnu dot org 2004-07-20 14:30 ` pinskia at gcc dot gnu dot org 2004-07-20 17:13 ` john dot spelis at 3dlabs dot com 2004-07-20 17:17 ` pinskia at gcc dot gnu dot org 2004-07-20 17:22 ` john dot spelis at 3dlabs dot com [this message]
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=20040720172239.14997.qmail@sourceware.org \ --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: linkBe 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).