From: "Henderson, Stuart" <Stuart.Henderson@analog.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: Problem cross-compiling trunk for bfin
Date: Thu, 17 Feb 2011 11:37:00 -0000 [thread overview]
Message-ID: <05E9E85E39C35B4D96ED3A3190E35A109CAEF87A0F@LIMKCMBX1.ad.analog.com> (raw)
In-Reply-To: <mcrmxlv1t6x.fsf@google.com>
Bug 47779 has been added to the database
Thanks Ian.
Stu
-----Original Message-----
From: Ian Lance Taylor [mailto:iant@google.com]
Sent: 16 February 2011 23:00
To: Henderson, Stuart
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problem cross-compiling trunk for bfin
"Henderson, Stuart" <Stuart.Henderson@analog.com> writes:
> r160579 | rsandifo | 2010-06-10 21:23:43 +0100 (Thu, 10 Jun 2010) | 7 lines
> gcc/
> * configure.ac (tm_include_list): Add insn-constants.h.
> * configure: Regenerate.
> * Makefile.in (GTM_H): Move insn-constants.h here from...
> (TM_H): ...here.
> * mkconfig.sh: Remove special handling for insn-constants.h.
>
> The change moves the inclusion of "insn-constants.h" from being conditional on:
> #if defined IN_GCC && !defined GENERATOR_FILE && !defined USED_FOR_TARGET
> to just:
> #if defined IN_GCC
>
> This causes insn-constants.h to be included here which defines various register macros that can then clash with the enum (of registers in the gregset_t array) in uClibc's sys/ucontext.h.
>
> Although I've only hit this with bfin, it seems like it could easily hit other architectures. Not having a deep enough understanding of the gcc ecosystem nor why the change was made, I was hoping someone could explain the best way to resolve this?
I doubt there is a clean way to solve this. Probably the simplest way
is to rename the conflicting constants in gcc/config/bfin/*.
Please open a bug report about this. See http://gcc.gnu.org/bugs/ .
Thanks.
Ian
prev parent reply other threads:[~2011-02-17 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 20:09 Henderson, Stuart
2011-02-16 23:02 ` Ian Lance Taylor
2011-02-17 11:37 ` Henderson, Stuart [this message]
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=05E9E85E39C35B4D96ED3A3190E35A109CAEF87A0F@LIMKCMBX1.ad.analog.com \
--to=stuart.henderson@analog.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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).