From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, 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: Thu, 23 Feb 2023 10:14:43 +0000 [thread overview]
Message-ID: <d7d9e545-a083-d7e7-5bc7-359c3218e684@foss.arm.com> (raw)
In-Reply-To: <oredqh1njl.fsf@lxoliva.fsfla.org>
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.
R.
>
>
> [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.
>
> Skipping the test or conditionally dropping the inline keyword breaks
> subsequent tests, so I'm XFAILing the expectation that vtable and rtti
> symbols are output on arm_eabi targets.
>
>
> for gcc/testsuite/ChangeLog
>
> PR c++/105224
> * g++.dg/modules/virt-2_a.C: XFAIL syms on arm_eabi.
> ---
> gcc/testsuite/g++.dg/modules/virt-2_a.C | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/testsuite/g++.dg/modules/virt-2_a.C b/gcc/testsuite/g++.dg/modules/virt-2_a.C
> index 580552be5a0d8..f5d68878f50fb 100644
> --- a/gcc/testsuite/g++.dg/modules/virt-2_a.C
> +++ b/gcc/testsuite/g++.dg/modules/virt-2_a.C
> @@ -22,6 +22,6 @@ export int Visit (Visitor *v)
> }
>
> // Emit here
> -// { dg-final { scan-assembler {_ZTVW3foo7Visitor:} } }
> -// { dg-final { scan-assembler {_ZTIW3foo7Visitor:} } }
> -// { dg-final { scan-assembler {_ZTSW3foo7Visitor:} } }
> +// { dg-final { scan-assembler {_ZTVW3foo7Visitor:} { xfail { arm_eabi } } } }
> +// { dg-final { scan-assembler {_ZTIW3foo7Visitor:} { xfail { arm_eabi } } } }
> +// { dg-final { scan-assembler {_ZTSW3foo7Visitor:} { xfail { arm_eabi } } } }
>
>
next prev parent reply other threads:[~2023-02-23 10:14 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 [this message]
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
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=d7d9e545-a083-d7e7-5bc7-359c3218e684@foss.arm.com \
--to=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).