From: Christophe Lyon <christophe.lyon@linaro.org>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Mike Stump <mikestump@comcast.net>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Kewen Lin <linkw@gcc.gnu.org>
Subject: Re: [PATCH] decay vect tests from run to link for pr95401
Date: Tue, 30 Apr 2024 14:39:08 +0200 [thread overview]
Message-ID: <CAPS5khYge-UROZ1F-WL080bFDK4eccnAJ_6j22eVG860PpgE-g@mail.gmail.com> (raw)
In-Reply-To: <orle4veoge.fsf@lxoliva.fsfla.org>
Hi Alexandre,
On Tue, 30 Apr 2024 at 01:31, Alexandre Oliva <oliva@adacore.com> wrote:
>
> On Apr 22, 2024, Richard Biener <richard.guenther@gmail.com> wrote:
>
> >> Regstrapped on x86_64-linux-gnu and ppc64el-linux-gnu. Also tested with
> >> gcc-13 on ppc64-vx7r2 and ppc-vx7r2. Ok to install?
>
> > That makes sense. OK
>
> >> for gcc/testsuite/ChangeLog
> >>
> >> * lib/target-supports.exp (check_vect_support_and_set_flags):
> >> Decay to link rather than compile.
>
> Alas, linking may fail because of an incompatible libc, as reported by
> Linaro with a link to their issue GNU-1206 (I'm not posting the link to
> the fully-Javascrippled Jira web page; it shows nothing useful, and I
> can't post feedback there) and to
> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_hard_eabi-build/10/artifact/artifacts/00-sumfiles/
> (where I could get useful information)
>
> I'm reverting the patch, and I'll see about some alternate approach that
> can accommodate this scenario after I return from LibrePlanet.
>
Indeed, that's another instance of the tricky multilibs configuration issues.
In this case:
- we configure GCC: --disable-multilib --with-mode=thumb
--with-cpu=cortex-m7 --with-float=hard --target=arm-eabi
(we disable multilibs to save build time)
- we run the tests with
qemu/-mthumb/-march=armv7e-m+fp.dp/-mtune=cortex-m7/-mfloat-abi=hard/-mfpu=auto
which matches the GCC configuration flags,
but the vect.exp tests add -mfpu=neon -mfloat-abi=softfp -march=armv7-a
and link fails because the toolchain does not support softfp libs
HTH
Thanks,
Christophe
> --
> Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
> Free Software Activist GNU Toolchain Engineer
> More tolerance and less prejudice are key for inclusion and diversity
> Excluding neuro-others for not behaving ""normal"" is *not* inclusive
next prev parent reply other threads:[~2024-04-30 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 7:38 [RFC] " Alexandre Oliva
2021-03-11 9:48 ` Richard Biener
2021-03-11 12:17 ` Richard Sandiford
2021-03-11 14:47 ` Alexandre Oliva
2021-03-12 7:42 ` Richard Biener
2024-04-22 10:05 ` [PATCH] " Alexandre Oliva
2024-04-22 19:10 ` Richard Biener
2024-04-29 23:30 ` Alexandre Oliva
2024-04-30 12:39 ` Christophe Lyon [this message]
2024-05-23 13:28 ` [PATCH] [testsuite] conditionalize dg-additional-sources on target and type Alexandre Oliva
2024-05-23 13:42 ` Christophe Lyon
2024-05-29 20:11 ` Mike Stump
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=CAPS5khYge-UROZ1F-WL080bFDK4eccnAJ_6j22eVG860PpgE-g@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=richard.guenther@gmail.com \
--cc=ro@cebitec.uni-bielefeld.de \
--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).