public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brad at mainstreetsoftworks dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16239] GCC 3.4.0 ICE on ppc64 (mozilla 1.7 compile,  -O1 -fno-exceptions issue)
Date: Mon, 28 Jun 2004 14:50:00 -0000	[thread overview]
Message-ID: <20040628144815.18733.qmail@sourceware.org> (raw)
In-Reply-To: <20040628022327.16239.brad@mainstreetsoftworks.com>


------- Additional Comments From brad at mainstreetsoftworks dot com  2004-06-28 14:48 -------
Ok, it is definitely reproducable on vanilla GCC 3.4.0 :

ppc64 objdir # gcc -v
Reading specs from /usr/local/gcc/lib/gcc/powerpc64-unknown-linux-gnu/3.4.0/specs
Configured with: ../gcc-3.4.0/configure --prefix=/usr/local/gcc --enable-shared
--host=powerpc64-unknown-linux-gnu --target=powerpc64-unknown-linux-gnu
--with-system-zlib --enable-languages=c,c++ --enable-threads=posix
--enable-long-long --disable-checking --disable-libunwind-exceptions
--enable-cstdio=stdio --enable-version-specific-runtime-libs --disable-werror
--enable-shared --enable-nls --without-included-gettext --disable-multilib
--enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix


ppc64 objdir # g++ -O1 -fno-exceptions -o /tmp/nsXULContentBuilder.o -c
/tmp/nsXULContentBuilder.CPP
nsXULContentBuilder.cpp: In member function `nsresult
nsXULContentBuilder::BuildContentFromTemplate(nsIContent*, nsIContent*,
nsIContent*, PRBool, nsIRDFResource*, PRBool, nsTemplateMatch*, nsIContent**,
PRInt32*)':
nsXULContentBuilder.cpp:825: error: insn does not satisfy its constraints:
(insn 6646 6645 6535 78 (set (reg/v/f:DI 63 31 [orig:979 data ] [979])
        (plus:DI (reg/v/f:DI 63 31 [orig:979 data ] [979])
            (const_int 232 [0xe8]))) 233 {*adddi3_internal1} (nil)
    (expr_list:REG_EQUIV (plus:DI (reg/f:DI 1 1)
            (const_int 232 [0xe8]))
        (nil)))
nsXULContentBuilder.cpp:825: internal compiler error: in
reload_cse_simplify_operands, at postreload.c:378
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

-- 


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


  parent reply	other threads:[~2004-06-28 14:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28  2:24 [Bug c++/16239] New: " brad at mainstreetsoftworks dot com
2004-06-28  2:26 ` [Bug c++/16239] " brad at mainstreetsoftworks dot com
2004-06-28  2:30 ` [Bug target/16239] " pinskia at gcc dot gnu dot org
2004-06-28  2:33 ` pinskia at gcc dot gnu dot org
2004-06-28  2:39 ` pinskia at gcc dot gnu dot org
2004-06-28  2:39 ` tgall at gentoo dot org
2004-06-28  2:41 ` tgall at gentoo dot org
2004-06-28  2:42 ` [Bug c++/16239] " brad at mainstreetsoftworks dot com
2004-06-28  5:01 ` [Bug target/16239] " pinskia at gcc dot gnu dot org
2004-06-28  5:40 ` pinskia at gcc dot gnu dot org
2004-06-28 14:50 ` brad at mainstreetsoftworks dot com [this message]
2004-07-24 22:36 ` dje at gcc dot gnu dot org
2004-07-27  1:51 ` cvs-commit at gcc dot gnu dot org
2004-07-27  1:53 ` cvs-commit at gcc dot gnu dot org
2004-07-27  1:57 ` dje at gcc dot gnu dot org
2005-01-05  9:17 ` cvs-commit at gcc dot gnu dot 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=20040628144815.18733.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: 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).