From: Dmitry Rozenshteyn <dbrozen@gmail.com>
To: crossgcc@sourceware.org
Subject: crosstool-NG 1.19 fails to build gcc 4.6.2 on host gcc version 4.7.3
Date: Thu, 08 May 2014 08:59:00 -0000 [thread overview]
Message-ID: <CADLBZ8te5xeVeLAD76H56XjHGWyqN1Biftbfw2GrN5uhpDfeMg@mail.gmail.com> (raw)
Hi,
when building ARM toolchain,
gcc 4.6.2 build fails on pass-1 core C compiler.
Host: Linux 3.8.0-35-generic i686, gcc 4.7.3
Target: cortex-a5
Issue is well-known: see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51969
To fix need to add an extra patch file into
patches/gcc/4.6.2/
Proposed
patches/gcc/4.6.2/001-gcc-bug-51969.patch content:
---------------
Author: jakub
Date: Tue Feb 14 23:31:42 2012
New Revision: 184239
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184239
Log:
PR bootstrap/51969
Backported from mainline
2011-11-08 Michael Matz <matz@suse.de>
* gengtype.c (write_field_root): Avoid out-of-scope access of newv.
Modified:
branches/gcc-4_6-branch/gcc/ChangeLog
branches/gcc-4_6-branch/gcc/gengtype.c
---
--- gcc-4_6-branch/gcc/gengtype.c 2012/02/14 23:26:47 184238
+++ gcc-4_6-branch/gcc/gengtype.c 2012/02/14 23:31:42 184239
@@ -3594,14 +3594,13 @@
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;
newv.name = ACONCAT ((v->name, ".", field_name, NULL));
-----------------------------------------------------------
Thanks,
Dmitry
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2014-05-08 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CADLBZ8te5xeVeLAD76H56XjHGWyqN1Biftbfw2GrN5uhpDfeMg@mail.gmail.com \
--to=dbrozen@gmail.com \
--cc=crossgcc@sourceware.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).