From: Iain Sandoe <idsandoe@googlemail.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: Alexandre Oliva <oliva@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>,
nickc@redhat.com, richard.earnshaw@arm.com, ramana.gcc@gmail.com,
kyrylo.tkachov@arm.com
Subject: Re: C++ modules and AAPCS/ARM EABI clash on inline key methods
Date: Fri, 24 Feb 2023 10:30:38 +0000 [thread overview]
Message-ID: <CC58C799-6AEE-4BAD-881C-33F9EC56A5D5@googlemail.com> (raw)
In-Reply-To: <ed21f950-684f-61ba-6de8-ad69ecbf5b77@foss.arm.com>
> On 24 Feb 2023, at 10:23, Richard Earnshaw via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
>
>
> On 23/02/2023 21:20, Alexandre Oliva wrote:
>> On Feb 23, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
>>> On Feb 23, 2023, Richard Earnshaw <Richard.Earnshaw@foss.arm.com> wrote:
>>>> On 22/02/2023 19:57, Alexandre Oliva wrote:
>>>>> On Feb 21, 2023, Richard Earnshaw <Richard.Earnshaw@foss.arm.com> wrote:
>>>>>
>>>>>> Rather than scanning for the triplet, a better test would be
>>>>>
>>>>>> { xfail { arm_eabi } }
>>>>>
>>>>> Indeed, thanks. Here's the updated patch, retested. Ok to install?
>>>> Based on Nathan's comments, we should just skip the test on arm_eabi,
>>>> it's simply not applicable.
>>> Like this, I suppose. Retested on x86_64-linux-gnu (trunk) and
>>> arm-wrs-vxworks7 (gcc-12). Ok to install?
>> Erhm, actually, that version still ran the assembler scans and failed.
>> This one skips the testset entirely.
>
> Yeah, I tried something like that and it didn't appear to work. Perhaps it's a bug in the way dg-do-module is implemented.
I think if you suppress the dg-do run line (with the target selector) then it will just do the default (which is to compile only?)
Skip seems like the correct thing to do here ..
Iain
>
>> [PR105224] C++ modules and AAPCS/ARM EABI clash on inline key methods
>> From: Alexandre Oliva <oliva@adacore.com>
>> g++.dg/modules/virt-2_a.C fails on arm-eabi and many other arm targets
>> that use the AAPCS variant. ARM is the only target that overrides
>> TARGET_CXX_KEY_METHOD_MAY_BE_INLINE. It's not clear to me which way
>> the clash between AAPCS and C++ Modules design should be resolved, but
>> currently it favors AAPCS and thus the test fails, so skip it on
>> arm_eabi.
>> for gcc/testsuite/ChangeLog
>> PR c++/105224
>> * g++.dg/modules/virt-2_a.C: Skip on arm_eabi.
>> ---
>> gcc/testsuite/g++.dg/modules/virt-2_a.C | 3 +++
>> 1 file changed, 3 insertions(+)
>> diff --git a/gcc/testsuite/g++.dg/modules/virt-2_a.C b/gcc/testsuite/g++.dg/modules/virt-2_a.C
>> index 580552be5a0d8..ede711c3e83be 100644
>> --- a/gcc/testsuite/g++.dg/modules/virt-2_a.C
>> +++ b/gcc/testsuite/g++.dg/modules/virt-2_a.C
>> @@ -1,3 +1,6 @@
>> +// AAPCS overrides TARGET_CXX_KEY_METHOD_MAY_BE_INLINE,
>> +// in a way that invalidates this test.
>> +// { dg-skip-if "TARGET_CXX_KEY_METHOD_MAY_BE_INLINE" { arm_eabi } }
>
> Given the logic of this macro, the text should be "!TARGET_CXX_METHOD_MAY_BE_INLINE".
>
> OK with that change.
>
> R.
>
>> // { dg-module-do run }
>> // { dg-additional-options -fmodules-ts }
>> export module foo;
next prev parent reply other threads:[~2023-02-24 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 7:32 Alexandre Oliva
2022-04-05 4:53 ` Alexandre Oliva
2023-02-17 6:09 ` Alexandre Oliva
2023-02-21 16:31 ` Richard Earnshaw
2023-02-21 16:48 ` Richard Earnshaw
2023-02-22 19:57 ` Alexandre Oliva
2023-02-23 10:14 ` Richard Earnshaw
2023-02-23 17:12 ` Alexandre Oliva
2023-02-23 21:20 ` Alexandre Oliva
2023-02-24 10:23 ` Richard Earnshaw
2023-02-24 10:30 ` Iain Sandoe [this message]
2023-02-24 14:39 ` Alexandre Oliva
2023-02-21 22:27 ` Nathan Sidwell
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=CC58C799-6AEE-4BAD-881C-33F9EC56A5D5@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=nathan@acm.org \
--cc=nickc@redhat.com \
--cc=oliva@adacore.com \
--cc=ramana.gcc@gmail.com \
--cc=richard.earnshaw@arm.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).