From: Segher Boessenkool <segher@kernel.crashing.org>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: "Kewen.Lin" <linkw@linux.ibm.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000: Rework option -mpowerpc64 handling [PR106680]
Date: Thu, 29 Sep 2022 12:26:43 -0500 [thread overview]
Message-ID: <20220929172643.GA25951@gate.crashing.org> (raw)
In-Reply-To: <5C0E6258-CBE2-4EFF-9D8C-DA26EECA0CAF@sandoe.co.uk>
On Thu, Sep 29, 2022 at 12:16:38AM +0100, Iain Sandoe wrote:
> > On 29 Sep 2022, at 00:04, Iain Sandoe <iain@sandoe.co.uk> wrote:
> > adding —with-tune=G5 to the configure line .. the cross-build then succeeded
> > (at "-O1 -g" as I was building to debug) - maybe that will provide a clue, but I’m
> > out of time for today.
>
> perhaps we also need a check that the m32 CPU has support for 64b insns?
>
> so perhaps —with-cpu-32=<G5, 970…> (or the moral equivalent) should be
> required?
In principle, yes. But -mpowerpc64 has been independently selectable
in the past. Compare to -maltivec, which often is used with -mcpu=750
and stuff like that.
We want to have less like this (much less), to reduce exponential
special cases and exponential testing requirements to something
manageable, but we also want to not break the world :-)
Segher
next prev parent reply other threads:[~2022-09-29 17:27 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
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 [this message]
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=20220929172643.GA25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=linkw@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).