From: Gerald Pfeifer <gerald@pfeifer.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Piotr Kubaj <pkubaj@anongoth.pl>,
gcc-patches@gcc.gnu.org, Andreas Tobler <andreast@freebsd.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: rs6000: add support for powerpc64le-unknown-freebsd
Date: Tue, 15 Dec 2020 00:29:45 +0100 (CET) [thread overview]
Message-ID: <6a26da98-5da9-1784-e815-11cf95fe42f1@pfeifer.com> (raw)
In-Reply-To: <20201214164604.GR2672@gate.crashing.org>
On Mon, 14 Dec 2020, Segher Boessenkool wrote:
>> + powerpc*le-*-*)
>> + tm_file="${tm_file} rs6000/sysv4le.h" ;;
>> + esac
> What an obvious filename ;-)
;-)
> The patch looks fine. Okay for trunk. Also okay for any backports you
> want (after waiting to see if it creates problems on trunk, as usual).
Thank you! Segher doesn't have write access, and usually I'd help out,
alas autoconf in GCC-land and me are, um, slightly divergent.
Any chance (one of you) can help and commit this?
To make this easier, I've created a proposal for a full ChangeLog
entry. :-)
2020-12-15 Piotr Kubaj <pkubaj@FreeBSD.org>
* config.gcc (powerpc*le-*-freebsd*): Add.
* configure.ac (powerpc*le-*-freebsd*): Ditto.
* config/rs6000/freebsd64.h (ASM_SPEC_COMMON): Use ENDIAN_SELECT.
(DEFAULT_ASM_ENDIAN): Add little endian support.
(LINK_OS_FREEBSD_SPEC64): Ditto.
Thank you,
Gerald
next prev parent reply other threads:[~2020-12-14 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:35 Piotr Kubaj
2020-12-14 16:46 ` Segher Boessenkool
2020-12-14 23:29 ` Gerald Pfeifer [this message]
2020-12-15 0:30 ` Segher Boessenkool
2020-12-16 22:58 ` Segher Boessenkool
2020-12-28 11:44 ` Gerald Pfeifer
2020-12-28 12:37 ` Segher Boessenkool
2021-09-10 23:26 ` Piotr Kubaj
2020-12-14 23:37 ` Gerald Pfeifer
2020-12-14 23:52 ` Piotr Kubaj
2020-12-16 22:23 ` Segher Boessenkool
2021-04-29 11:37 ` Piotr Kubaj
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=6a26da98-5da9-1784-e815-11cf95fe42f1@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=andreast@freebsd.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pkubaj@anongoth.pl \
--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).