public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: [PATCH 8/8] Add a common .md file and define standard constraints there
Date: Tue, 10 Jun 2014 20:59:00 -0000	[thread overview]
Message-ID: <53977194.1020401@redhat.com> (raw)
In-Reply-To: <87tx7z822q.fsf@talisman.default>

On 06/05/14 15:43, Richard Sandiford wrote:
> This final patch uses a common .md file to define all standard
> constraints except 'g'.  It then gets rid of explicit case statements
> for the standard constraints, except in two cases:
>
> (1) recog.c:asm_operand_ok still needs to handle 'o' specially for
>      targets like ia64 that don't have offsettable addresses.  See the
>      comment there for justification.
>
> (2) the trickier cases in reload.  I'm not changing those more than I have to.
Can't argue with #2 ;-)  reload gets less and less important every day, 
so I see less and less value hacking too much on it.

>
> I did wonder about defining a new rtl construct that could be used for 'g',
> so that even that special case goes away.  In the end I think it would be
> a false abstraction though.  No other constraint allows (or IMO should allow)
> all three of a register class, a base-reloadable memory and a constant,
> so handling it in the lookup_constraint paths would make things more
> complicated rather than less.
OK.

>
> Note that the s390 'e' constraint is TARGET_MEM_CONSTRAINT, which is now
> defined in the common file.
>
> I put the common .md file in the main gcc/ directory by analogy with
> defaults.h and common.opt.  It could instead go in config/ or config/common/,
> if those sound better.
Seems fine to me, I don't feel a need to bikeshed here.


Does the comment before indep_constraints in genoutput need updating? 
The constraints in common.md are machine independent, but aren't listed 
in indep_constraints in genoutput.c

Approved with whatever language you want to use for that comment.

Jeff

  reply	other threads:[~2014-06-10 20:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 21:25 [PATCH 0/8] Constraint matching TLC Richard Sandiford
2014-06-05 21:27 ` [PATCH 1/8] Faster checks for constraint types Richard Sandiford
2014-06-10 18:42   ` Jeff Law
2014-06-05 21:29 ` [PATCH 2/8] Speed up lookup_constraint Richard Sandiford
2014-06-10 18:41   ` Jeff Law
2014-06-05 21:31 ` [PATCH 3/8] Speed up constraint_satisfied_p Richard Sandiford
2014-06-10 18:42   ` Jeff Law
2014-06-05 21:32 ` [PATCH 4/8] Remove old macros and make lookup_constraint explicit Richard Sandiford
2014-06-10 20:53   ` Jeff Law
2014-06-05 21:33 ` [PATCH 5/8] Remove unused operand_alternative fields Richard Sandiford
2014-06-10 18:43   ` Jeff Law
2014-06-05 21:38 ` [PATCH 6/8] Treat 'I'-'P' as separate subtype Richard Sandiford
2014-06-10 18:48   ` Jeff Law
2014-06-05 21:41 ` [PATCH 7/8] Remove 'I'-'P' and 'G'/'H' cases Richard Sandiford
2014-06-10 18:50   ` Jeff Law
2014-06-05 21:43 ` [PATCH 8/8] Add a common .md file and define standard constraints there Richard Sandiford
2014-06-10 20:59   ` Jeff Law [this message]
2014-06-11 17:01     ` Richard Sandiford
2014-06-13 20:06       ` Steve Ellcey
2014-06-14  7:49         ` Richard Sandiford
2014-06-16 14:48           ` Steve Ellcey
2014-06-12 19:24   ` Segher Boessenkool
2014-06-12 19:39     ` Paul_Koning
2014-06-12 21:19       ` Segher Boessenkool
2014-06-14  9:58         ` Richard Sandiford

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=53977194.1020401@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdsandiford@googlemail.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).