public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63195] New: [5.0 regression] stage3 build/gengtype miscompiled
Date: Sat, 06 Sep 2014 16:58:00 -0000	[thread overview]
Message-ID: <bug-63195-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63195

            Bug ID: 63195
           Summary: [5.0 regression] stage3 build/gengtype miscompiled
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: build, wrong-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: schwab@linux-m68k.org
                CC: segher at kernel dot crashing.org
            Target: powerpc64-*-*

r214077 is causing the stage3 build/gengtype to be miscompiled on ppc64.

build/gengtype  \   
                    -S ../../gcc/gcc -I gtyp-input.list -w tmp-gtype.state
../../gcc/gcc/rtl.h:214: undefined type `rtunion'
../../gcc/gcc/java/builtins.c:82: undefined type `builtin_creator_function'
gengtype: didn't write state file tmp-gtype.state after errors
make[2]: *** [s-gtype] Error 1


             reply	other threads:[~2014-09-06 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06 16:58 schwab@linux-m68k.org [this message]
2014-09-06 17:12 ` [Bug target/63195] " schwab@linux-m68k.org
2014-09-08  8:39 ` rguenth at gcc dot gnu.org
2014-09-09 18:49 ` segher at gcc dot gnu.org
2014-09-09 19:00 ` segher 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-63195-4@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).