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: Wed, 28 Sep 2022 16:30:49 -0500 [thread overview]
Message-ID: <20220928213049.GU25951@gate.crashing.org> (raw)
In-Reply-To: <5B4DCBBB-3237-4A9F-ACCA-6669DE6905B8@sandoe.co.uk>
Hi!
On Wed, Sep 28, 2022 at 05:18:47PM +0100, Iain Sandoe wrote:
> > On 28 Sep 2022, at 07:37, Iain Sandoe <iain@sandoe.co.uk> wrote:
> >> On 28 Sep 2022, at 06:30, Kewen.Lin via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> >> PR106680 shows that -m32 -mpowerpc64 is different from
> >> -mpowerpc64 -m32, this is determined by the way how we
> >> handle option powerpc64 in rs6000_handle_option.
> >>
> >> Segher pointed out this difference should be taken as
> >> a bug and we should ensure that option powerpc64 is
> >> independent of -m32/-m64. So this patch removes the
> >> handlings in rs6000_handle_option and add some necessary
> >> supports in rs6000_option_override_internal instead.
> >>
> >> With this patch, if users specify -m{no-,}powerpc64, the
> >> specified value is honoured, otherwise, for 64bit it
> >> always enables OPTION_MASK_POWERPC64 while for 32bit
> >> it disables OPTION_MASK_POWERPC64 if OS_MISSING_POWERPC64.
It probably shouldn't have to disable it, it can only be on if it is
explicitly enabled by the user? So warning would be much better than
implicitly disabling it.
> Perhaps a small exposition on the target:
>
> powerpc-apple-darwin, is perhaps somewhat unusual in that it is nominally a 32b kernel, but the OS supports 64b processes on suitable hardware
Just like Linux was before there was powerpc64-linux. I think it should
still work even?
> (and the OS does preserve the upper bits of 64b regs in the context).
That works on Linux as well. What still does not work is user-mode
context switches in 32-bit processes (so setjmp and getcontext stuff).
> Of course, powerpc-darwin is not a blocker for anything, it should not hold you up (but sometimes it
> manages to find a glitch missed elsewhere).
It is stage 1, nothing blocks nothing :-) But indeed this looks like a
bug not specific to Darwin. It would be nice if it was fixed before
this goes in.
> I will try to take a look at this this evening see if I can throw
> any more light on it.
Thanks!
Segher
next prev parent reply other threads:[~2022-09-28 21:31 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 [this message]
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=20220928213049.GU25951@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).