From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: "Kewen.Lin" <linkw@linux.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] rs6000: Rework option -mpowerpc64 handling [PR106680]
Date: Mon, 5 Feb 2024 11:38:30 +0100 [thread overview]
Message-ID: <2c854fba-8fc1-4c00-8562-396c0a0acdab@embedded-brains.de> (raw)
In-Reply-To: <c8dc1afd-7d34-e3f3-6901-1d670bef2c0e@linux.ibm.com>
Hello,
On 27.12.22 11:16, Kewen.Lin via Gcc-patches wrote:
> Hi Segher,
>
> on 2022/12/24 04:26, Segher Boessenkool wrote:
>> Hi!
>>
>> On Wed, Oct 12, 2022 at 04:12:21PM +0800, Kewen.Lin 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.
>>
>> Sorry for the late review.
>>
>>> + /* Don't expect powerpc64 enabled on those OSes with OS_MISSING_POWERPC64,
>>> + since they don't support saving the high part of 64-bit registers on
>>> + context switch. If the user explicitly specifies it, we won't interfere
>>> + with the user's specification. */
>>
>> It depends on the OS, and what you call "context switch". For example
>> on Linux the context switches done by the kernel are fine, only things
>> done by setjmp/longjmp and getcontext/setcontext are not. So just be a
>> bit more vague here? "Since they do not save and restore the high half
>> of the GPRs correctly in all cases", something like that?
>>
>> Okay for trunk like that. Thanks!
>>
>
> Thanks! Adjusted as you suggested and committed in r13-4894-gacc727cf02a144.
I am a bit late, however, this broke the 32-bit support for -mcpu=e6500.
For RTEMS, I have the following multilibs:
MULTILIB_REQUIRED += mcpu=e6500/m32
MULTILIB_REQUIRED += mcpu=e6500/m32/mvrsave
MULTILIB_REQUIRED += mcpu=e6500/m32/msoft-float/mno-altivec
MULTILIB_REQUIRED += mcpu=e6500/m64
MULTILIB_REQUIRED += mcpu=e6500/m64/mvrsave
I configured GCC as a bi-arch compiler (32-bit and 64-bit). It seems you
removed the -m32 handling, so I am not sure how to approach this issue.
I added a test case to the PR:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106680
--
embedded brains GmbH & Co. KG
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2024-02-05 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 8:12 Kewen.Lin
2022-10-12 8:57 ` Iain Sandoe
2022-10-13 10:09 ` Iain Sandoe
2022-10-17 8:59 ` Kewen.Lin
2022-11-30 8:33 ` PING^1 " Kewen.Lin
2022-12-14 11:24 ` PING^2 " Kewen.Lin
2022-12-23 20:26 ` Segher Boessenkool
2022-12-27 10:16 ` Kewen.Lin
2024-02-05 10:38 ` Sebastian Huber [this message]
2024-02-05 11:49 ` Kewen.Lin
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=2c854fba-8fc1-4c00-8562-396c0a0acdab@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--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).