From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Jeff Law <law@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Introduce be/le selectors
Date: Fri, 25 May 2018 09:37:00 -0000 [thread overview]
Message-ID: <9fcc8cb9-b20d-2abd-5f53-ccf50f230b54@arm.com> (raw)
In-Reply-To: <20180524172842.GB17342@gate.crashing.org>
On 24/05/18 18:28, Segher Boessenkool wrote:
> On Wed, May 23, 2018 at 10:07:18AM +0100, Richard Earnshaw (lists) wrote:
>> On 22/05/18 22:21, Jeff Law wrote:
>>> On 05/21/2018 03:46 PM, Segher Boessenkool wrote:
>>>> This patch creates "be" and "le" selectors, which can be used by all
>>>> architectures, similar to ilp32 and lp64.
>
>>>> 2017-05-21 Segher Boessenkool <segher@kernel.crashing.org>
>>>>
>>>> gcc/testsuite/
>>>> * lib/target-supports.exp (check_effective_target_be): New.
>>>> (check_effective_target_le): New.
>>> I think this is fine. "be" "le" are used all over the place in gcc and
>>> the kernel to denote big/little endian.
>>
>> except when el and eb are used for perversity... :-)
>
> It should have been -BE and -EL, because that is what it means. That
> also avoids the -l/-L problem -le and -LE would have ;-)
>
> (Confusing? Yes, little-endian is confusing).
I beg to differ. Big endian is the confusing one... :-)
R.
>
>
> Segher
>
next prev parent reply other threads:[~2018-05-25 9:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 21:59 Segher Boessenkool
2018-05-21 22:12 ` Rainer Orth
2018-05-21 23:02 ` Segher Boessenkool
2018-05-22 21:36 ` Jeff Law
2018-05-23 9:33 ` Richard Earnshaw (lists)
2018-05-24 17:31 ` Segher Boessenkool
2018-05-25 9:37 ` Richard Earnshaw (lists) [this message]
2018-05-25 17:28 ` Segher Boessenkool
2018-05-23 17:53 ` Segher Boessenkool
2018-06-27 16:01 ` [PATCH] Backport " Kelvin Nilsen
2018-06-27 18:39 ` Jeff Law
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=9fcc8cb9-b20d-2abd-5f53-ccf50f230b54@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.org \
/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).