From: Christophe LYON <christophe.lyon@foss.st.com>
To: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] arm: Fix multilib mapping for CDE extensions [PR100856]
Date: Mon, 23 Aug 2021 10:58:05 +0200 [thread overview]
Message-ID: <3455f96c-71e3-f04a-5836-4af72207da9f@foss.st.com> (raw)
In-Reply-To: <ea7bc912-7722-6e81-ba7e-6b30af3ed975@foss.st.com>
ping?
On 16/08/2021 13:51, Christophe LYON via Gcc-patches wrote:
> ping?
>
> On 11/08/2021 16:06, Christophe Lyon wrote:
>> ping?
>> https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575310.html
>> <https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575310.html>
>>
>>
>> On Wed, Aug 4, 2021 at 11:13 AM Christophe Lyon via Gcc-patches
>> <gcc-patches@gcc.gnu.org <mailto:gcc-patches@gcc.gnu.org>> wrote:
>>
>> ping?
>>
>> On Thu, 15 Jul 2021 at 15:07, Christophe LYON via Gcc-patches
>> <gcc-patches@gcc.gnu.org <mailto:gcc-patches@gcc.gnu.org>> wrote:
>> >
>> > This is a followup to Srinath's recent patch: the newly added
>> test is
>> > failing e.g. on arm-linux-gnueabihf without R/M profile multilibs.
>> >
>> > It is also failing on arm-eabi with R/M profile multilibs if the
>> > execution engine does not support v8.1-M instructions.
>> >
>> > The patch avoids this by adding
>> check_effective_target_FUNC_multilib
>> > in target-supports.exp which effectively checks whether the target
>> > supports linking and execution, like what is already done for
>> other
>> > ARM effective targets. pr100856.c is updated to use it instead of
>> > arm_v8_1m_main_cde_mve_ok (which makes the testcase a bit of a
>> > duplicate with check_effective_target_FUNC_multilib).
>> >
>> > In addition, I noticed that requiring MVE does not seem
>> necessary and
>> > this enables the test to pass even when targeting a CPU without
>> MVE:
>> > since the test does not involve actual CDE instructions, it can
>> pass
>> > on other architecture versions. For instance, when requiring
>> MVE, we
>> > have to use cortex-m55 under QEMU for the test to pass because the
>> > memset() that comes from v8.1-m.main+mve multilib uses LOB
>> > instructions (DLS) (memset is used during startup). Keeping
>> > arm_v8_1m_main_cde_mve_ok would mean we would enable the test
>> provided
>> > we have the right multilibs, causing a runtime error if the
>> simulator
>> > does not support LOB instructions (e.g. when targeting cortex-m7).
>> >
>> > I do not update sourcebuild.texi since the CDE effective
>> targets are
>> > already collectively documented.
>> >
>> > Finally, the patch fixes two typos in comments.
>> >
>> > 2021-07-15 Christophe Lyon <christophe.lyon@foss.st.com
>> <mailto:christophe.lyon@foss.st.com>>
>> >
>> > PR target/100856
>> > gcc/
>> > * config/arm/arm.opt: Fix typo.
>> > * config/arm/t-rmprofile: Fix typo.
>> >
>> > gcc/testsuite/
>> > * gcc.target/arm/acle/pr100856.c: Use
>> arm_v8m_main_cde_multilib
>> > and arm_v8m_main_cde.
>> > * lib/target-supports.exp: Add
>> > check_effective_target_FUNC_multilib for ARM CDE.
>> >
>> >
>>
next prev parent reply other threads:[~2021-08-23 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 13:04 Christophe LYON
2021-08-04 9:11 ` Christophe Lyon
2021-08-11 14:06 ` Christophe Lyon
2021-08-16 11:51 ` Christophe LYON
2021-08-23 8:58 ` Christophe LYON [this message]
2021-08-23 9:03 ` Kyrylo Tkachov
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=3455f96c-71e3-f04a-5836-4af72207da9f@foss.st.com \
--to=christophe.lyon@foss.st.com \
--cc=gcc-patches@gcc.gnu.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).