From: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Adding constraints.md to my port
Date: Tue, 14 Jul 2009 20:31:00 -0000 [thread overview]
Message-ID: <c568a2600907141331r4bd5b7e4jb5083fbc68d6d435@mail.gmail.com> (raw)
In-Reply-To: <m3prc3avo0.fsf@google.com>
Ok, so actually, my cpu.h file had some of those included. I've
removed them and am now filling in the constraints.md file with what
is needed. I also so that they were obsolete in the GCC internals,
I'll be moving everything to the constraints then.
Thank you for your help,
Jc
On Tue, Jul 14, 2009 at 3:53 PM, Ian Lance Taylor<iant@google.com> wrote:
> Jean Christophe Beyler <jean.christophe.beyler@gmail.com> writes:
>
>> In file included from ./tm_p.h:5,
>> from /home/toto/gcc-4.3.2/gcc/c-pragma.c:35:
>> ./tm-preds.h:40:1: warning: "CONSTRAINT_LEN" redefined
>> In file included from ./tm.h:6,
>> from /home/toto/gcc-4.3.2/gcc/c-pragma.c:24:
>> /home/toto/gcc-4.3.2/gcc/defaults.h:797:1: warning: this is the
>> location of the previous definition
>
> See defaults.h:
>
> #if !defined CONSTRAINT_LEN \
> && !defined REG_CLASS_FROM_LETTER \
> && !defined REG_CLASS_FROM_CONSTRAINT \
> && !defined CONST_OK_FOR_LETTER_P \
> && !defined CONST_OK_FOR_CONSTRAINT_P \
> && !defined CONST_DOUBLE_OK_FOR_LETTER_P \
> && !defined CONST_DOUBLE_OK_FOR_CONSTRAINT_P \
> && !defined EXTRA_CONSTRAINT \
> && !defined EXTRA_CONSTRAINT_STR \
> && !defined EXTRA_MEMORY_CONSTRAINT \
> && !defined EXTRA_ADDRESS_CONSTRAINT
>
> #define USE_MD_CONSTRAINTS
>
>
> Make sure that your CPU.h file does not define any of those macros.
>
> Ian
>
next prev parent reply other threads:[~2009-07-14 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 18:30 Jean Christophe Beyler
2009-07-14 19:53 ` Ian Lance Taylor
2009-07-14 20:31 ` Jean Christophe Beyler [this message]
2009-07-15 5:30 ` Paolo Bonzini
2009-07-15 15:22 ` Jean Christophe Beyler
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=c568a2600907141331r4bd5b7e4jb5083fbc68d6d435@mail.gmail.com \
--to=jean.christophe.beyler@gmail.com \
--cc=gcc@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).