public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/51969] [4.7 regression] gcc 4.7 unable to build gcc 4.6
Date: Mon, 23 Jan 2012 18:35:00 -0000	[thread overview]
Message-ID: <bug-51969-4-DWCueaBsuZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51969-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-01-23 18:21:14 UTC ---
The following patch (applied to 4.6) fixes the problem for me:

diff --git a/gcc/gengtype.c b/gcc/gengtype.c
index abf17f8..550d3bb 100644
--- a/gcc/gengtype.c
+++ b/gcc/gengtype.c
@@ -3594,13 +3594,13 @@ write_field_root (outf_p f, pair_p v, type_p type,
const char *name,
                  int has_length, struct fileloc *line, const char *if_marked,
                  bool emit_pch, type_p field_type, const char *field_name)
 {
+  struct pair newv;
   /* If the field reference is relative to V, rather than to some
      subcomponent of V, we can mark any subarrays with a single stride.
      We're effectively treating the field as a global variable in its
      own right.  */
   if (v && type == v->type)
     {
-      struct pair newv;

       newv = *v;
       newv.type = field_type;


  reply	other threads:[~2012-01-23 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 17:05 [Bug bootstrap/51969] New: " markus at trippelsdorf dot de
2012-01-23 18:35 ` markus at trippelsdorf dot de [this message]
2012-01-23 18:49 ` [Bug bootstrap/51969] [4.6 " jakub at gcc dot gnu.org
2012-01-24  7:50 ` ralf_corsepius at rtems dot org
2012-01-24 13:38 ` rguenth at gcc dot gnu.org
2012-02-14 23:32 ` [Bug bootstrap/51969] [4.6 regression] trunk gcc " jakub at gcc dot gnu.org
2012-02-14 23:46 ` jakub at gcc dot gnu.org
2012-04-24  4:22 ` pinskia at gcc dot gnu.org
2012-06-11  9:10 ` jye2 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-51969-4-DWCueaBsuZ@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).