From: Joern Rennecke <joern.rennecke@superh.com>
To: Ulrich Weigand <weigand@immd1.informatik.uni-erlangen.de>
Cc: gcc@gcc.gnu.org
Subject: Re: RFD: constraint letter suffixes
Date: Mon, 06 Jan 2003 14:21:00 -0000 [thread overview]
Message-ID: <3E1980FB.E1D7042B@superh.com> (raw)
In-Reply-To: <200212241410.PAA08511@faui11.informatik.uni-erlangen.de>
Ulrich Weigand wrote:
>
> Joern Rennecke wrote:
>
> >EXTRA_MEMORY_CONSTRAINT is defined only by one port, and
> >EXTRA_ADDRESS_CONSTRAINT by none, so I suppose adding another
> >parameter to these macros isn't too much of a switch burden.
>
> I have a patch that will introduce EXTRA_ADDRESS_CONSTRAINT
> to the s390 port as well; I had been holding this until the
> 3.4 development was opened.
>
> In any case, I don't mind another parameter there, in particular
> if I get more constraint letters from it ;-)
The numbers of the letters will stay the same, but you will be able
to use one letter for multiple different constraints by using
a suffix, e.g. L0, L1, L2.
> Will it be possible to have more different integer constant
> constraints with your patch? This would be helpful for s390 ...
Yes, this was actually the motivation of this patch. The SH also
needs more different integer constraints.
--
--------------------------
SuperH (UK) Ltd.
2410 Aztec West / Almondsbury / BRISTOL / BS32 4QX
T:+44 1454 465658
next prev parent reply other threads:[~2003-01-06 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 10:47 Ulrich Weigand
2003-01-06 14:21 ` Joern Rennecke [this message]
2003-01-06 17:50 ` Joern Rennecke
2003-01-13 21:28 ` Ulrich Weigand
2003-01-14 0:28 ` Joern Rennecke
2003-01-07 21:54 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
2002-09-12 7:01 Joern Rennecke
2002-12-23 9:46 ` Joern Rennecke
2002-12-24 10:08 ` Joern Rennecke
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=3E1980FB.E1D7042B@superh.com \
--to=joern.rennecke@superh.com \
--cc=gcc@gcc.gnu.org \
--cc=weigand@immd1.informatik.uni-erlangen.de \
/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).