From: "Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>
To: Andreas Schwab <schwab@suse.de>
Cc: <libc-alpha@sourceware.org>, <tuliom@linux.vnet.ibm.com>
Subject: Re: [PATCH v3] powerpc64*: fix the order of implied sysdeps directories
Date: Thu, 08 Mar 2018 20:49:00 -0000 [thread overview]
Message-ID: <20180308174909.7cbf8292@keller.br.ibm.com> (raw)
In-Reply-To: <mvmk1unou9g.fsf@suse.de>
On Thu, 08 Mar 2018, Andreas Schwab wrote:
>On Mär 07 2018, "Gabriel F. T. Gomes" <gabriel@inconstante.eti.br> wrote:
>
>> Moving the whole of powerpc64 to powerpc64-common, leaves powerpc64 empty,
>> which I can then fill with files that are specific to big-endian.
>
>Ok, how about this then: put the BE file in .../powerpc64/be, the LE
>files in .../powerpc64/le, and keep the common files in .../powerpc64?
While I can see the advantage of keeping the common files in .../powerpc64
(i.e.: most of the renamings in this patch disappear), I am not sure about
changing the name of the machine directories. Notice that the configure
script will guess the name of the machine from the compiler triplet, so
big-endian automatically brings .../powerpc64, and little-endian
brings .../powerpc64le.
So, moving machine directories to .../powerpc64/{be,le}, means that
something needs to convert powerpc64 (from the triplet) to powerpc64/be
and powerpc64le to powerpc64/le. Moreover, I think that this will
implicitly imply ".../powerpc64" for both big-endian and little-endian.
With that in mind, would you still suggest this change (maybe you had
something else in mind, which I couldn't grasp)?
next prev parent reply other threads:[~2018-03-08 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 16:36 Gabriel F. T. Gomes
2018-03-07 16:44 ` Andreas Schwab
2018-03-07 17:15 ` Gabriel F. T. Gomes
2018-03-08 8:18 ` Andreas Schwab
2018-03-08 20:49 ` Gabriel F. T. Gomes [this message]
2018-03-09 16:39 ` Joseph Myers
2018-03-13 16:24 ` Gabriel F. T. Gomes
2018-03-12 9:04 ` Andreas Schwab
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=20180308174909.7cbf8292@keller.br.ibm.com \
--to=gabriel@inconstante.eti.br \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=tuliom@linux.vnet.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).