From: Iain Sandoe <iain@sandoe.co.uk>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] rs6000: Rework option -mpowerpc64 handling [PR106680]
Date: Thu, 29 Sep 2022 17:14:40 +0100 [thread overview]
Message-ID: <4F795875-4D05-4FFE-8DF2-50AF20E19139@sandoe.co.uk> (raw)
In-Reply-To: <826f30b1-a3fe-4227-1874-5e4f5a1f6d56@linux.ibm.com>
Hi Kewen,
> On 29 Sep 2022, at 10:12, Kewen.Lin via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> on 2022/9/29 16:16, Iain Sandoe wrote:
>>>
>>> I'm testing the attached diff which can be applied on top of the previous proposed patch
>>> on ppc64 and ppc64le, could you help to test it can fix the issue?
>>
>> It does work on a cross from x86_64-darwin => powerpc-darwin, I can also do compile-only
>> tests there with a dummy board and the new tests pass with one minor tweak as described
>> below.
>> full regstrap on the G5 will take a day or so .. but I’ll do the C target tests first to get a heads up
>
> Thanks! I think the C target tests is enough for now.
Bootstrap (powerpc-darwin9 on G5) succeeded and the C tests look nominal.
Cheers
Iain
next prev parent reply other threads:[~2022-09-29 16:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 5:30 Kewen.Lin
2022-09-28 6:37 ` Iain Sandoe
2022-09-28 16:18 ` Iain Sandoe
2022-09-28 19:09 ` Iain Sandoe
2022-09-29 5:45 ` Kewen.Lin
2022-09-29 8:16 ` Iain Sandoe
2022-09-29 9:12 ` Kewen.Lin
2022-09-29 16:14 ` Iain Sandoe [this message]
2022-09-29 17:04 ` Segher Boessenkool
2022-09-29 18:25 ` Iain Sandoe
2022-09-29 18:37 ` Segher Boessenkool
2022-09-30 9:26 ` Kewen.Lin
2022-09-29 17:11 ` Segher Boessenkool
2022-09-30 12:15 ` Kewen.Lin
2022-10-03 21:15 ` Segher Boessenkool
2022-10-10 2:15 ` Kewen.Lin
2022-10-10 13:58 ` Segher Boessenkool
2022-10-12 8:26 ` Kewen.Lin
2022-09-28 21:30 ` Segher Boessenkool
2022-09-28 23:04 ` Iain Sandoe
2022-09-28 23:16 ` Iain Sandoe
2022-09-29 17:26 ` Segher Boessenkool
2022-09-29 17:18 ` Segher Boessenkool
2022-09-29 18:33 ` Iain Sandoe
2022-09-29 18:50 ` Segher Boessenkool
2022-09-28 22:04 ` Segher Boessenkool
2022-09-29 6:16 ` Kewen.Lin
2022-09-29 18:56 ` 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=4F795875-4D05-4FFE-8DF2-50AF20E19139@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.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).