public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH 1/7] PowerPC tests: Add prefixed/pcrel tests.
Date: Mon, 8 Jun 2020 20:09:50 -0500	[thread overview]
Message-ID: <20200609010950.GX31009@gate.crashing.org> (raw)
In-Reply-To: <1591041222-24243-2-git-send-email-meissner@linux.ibm.com>

Hi!

On Mon, Jun 01, 2020 at 03:53:36PM -0400, Michael Meissner wrote:
> +# Return 1 if the target generates PC-relative instructions automatically for
> +# the PowerPC 'future' machine.

"... automatically, for configurations that allow it"?

If the selector was only for the "future" target, that should be part of
the name; but it is not, that is just a detail of the actual test.

> +proc check_effective_target_powerpc_pcrel { } {
> +    return [check_no_messages_and_pattern powerpc_pcrel \
> +	{\mpla\M} assembly {
> +	    static unsigned short s;
> +	    unsigned short *p_foo (void) { return &s; }
> +	} {-O2 -mcpu=future}]
> +}


> +# Return 1 if the target generates prefixed instructions automatically for the
> +# PowerPC 'future' machine.

Same here.

(It is important that the description for each selector is clear and
accurate, and guides the potential user to what selector to use where).

Okay for trunk with that changed.  Thanks!


Segher

  reply	other threads:[~2020-06-09  1:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 19:53 PowerPC tests for -mcpu=future Michael Meissner
2020-06-01 19:53 ` [PATCH 1/7] PowerPC tests: Add prefixed/pcrel tests Michael Meissner
2020-06-09  1:09   ` Segher Boessenkool [this message]
2020-06-01 19:53 ` [PATCH 2/7] PowerPC tests: Add PLI/PADDI tests Michael Meissner
2020-06-25 16:52   ` Segher Boessenkool
2020-06-27  5:49     ` Michael Meissner
2020-06-27 18:55       ` Segher Boessenkool
2020-06-29 18:23         ` Michael Meissner
2020-06-29 18:42           ` Segher Boessenkool
2020-06-30  5:58             ` Michael Meissner
2020-07-01  0:51               ` Segher Boessenkool
2020-06-27  5:57     ` Michael Meissner
2020-06-27 18:58       ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 3/7] PowerPC tests: Add prefixed vs. DS/DQ instruction tests Michael Meissner
2020-06-25 16:54   ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 4/7] PowerPC test: Add prefixed no update test Michael Meissner
2020-06-25 16:58   ` Segher Boessenkool
2020-06-01 19:53 ` [PATCH 5/7] PowerPC tests: Prefixed insn with large offsets Michael Meissner
2020-06-01 19:53 ` [PATCH 6/7] PowerPC tests: Add PC-relative tests Michael Meissner
2020-06-01 22:45   ` will schmidt
2020-06-03  3:43     ` Michael Meissner
2020-06-01 19:53 ` [PATCH 7/7] PowerPC test: Add prefixed stack protect test Michael Meissner
2020-06-25 17:18   ` Segher Boessenkool
2020-06-27  5:50     ` Michael Meissner
2020-06-27 18:44       ` Segher Boessenkool
2020-06-01 22:45 ` PowerPC tests for -mcpu=future will schmidt
2020-06-04 17:03 ` [PATCH 5/7, V2] PowerPC tests: Prefixed insn with large offsets Michael Meissner
2020-06-25 17:09   ` Segher Boessenkool
2020-06-27  5:55     ` Michael Meissner
2020-06-27 18:53       ` Segher Boessenkool
2020-06-04 17:05 ` [PATCH 6/7, V2] PowerPC tests: Add PC-relative tests Michael Meissner
2020-06-25 17:15   ` Segher Boessenkool

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=20200609010950.GX31009@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meissner@linux.ibm.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).