public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dj at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/35834]  New: building libiberty fails in build2_stat for -mcpu=m32c as of r133403
Date: Sat, 05 Apr 2008 15:36:00 -0000	[thread overview]
Message-ID: <bug-35834-681@http.gcc.gnu.org/bugzilla/> (raw)

$ ./cc1 -fpreprocessed /tmp/cplus-dem.i -quiet -dumpbase cplus-dem.c
-mcpu=m32cm -auxbase-strip cplus-dem.o -g -O2 -W -Wall -Wwrite-strings
-Wc++-compat -Wstrict-prototypes -pedantic -o cplus-dem.s
../../../../gcc/libiberty/cplus-dem.c: In function
'cplus_demangle_name_to_style':
../../../../gcc/libiberty/cplus-dem.c:807: internal compiler error: in
build2_stat, at tree.c:3107


-- 
           Summary: building libiberty fails in build2_stat for -mcpu=m32c
                    as of r133403
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dj at redhat dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: m32c-elf


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


             reply	other threads:[~2008-04-05 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 15:36 dj at redhat dot com [this message]
2008-04-05 15:37 ` [Bug tree-optimization/35834] " dj at redhat dot com
2008-04-05 15:57 ` rguenth at gcc dot gnu dot org
2008-04-05 16:09 ` rguenth at gcc dot gnu dot org
2008-04-08  9:55 ` rguenth at gcc dot gnu dot org
2008-04-08  9:56 ` rguenth 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=bug-35834-681@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).