Marc Poulhiès writes:
> Require effective target fpic for newly added test.
>
> gcc/testsuite/
> * g++.dg/ext/visibility/visibility-local-extern1.C: Add missing
> dg-require-effective-target fpic.
>
> Tested on x86_64-linux. Ok for master?
>
> ---
> gcc/testsuite/g++.dg/ext/visibilit
Hi,
> Sorry, just realised I'd never replied to this.
No worries! I also took a very long time to reply, sorry.
> The problem is that we only enforce lane bounds via calls to
> __builtin_aarch64_im_lane_boundsi. In previous releases, the check
> only happend at RTL expansion time, so the check
Eric Botcazou writes:
>> The new variables seem to be unused, so I think slightly stronger
>> DCE could remove the calls even after the patch. Perhaps the containing
>> functions should take an int32x4_t *ptr or something, with the calls
>> assigning to different ptr[] indices.
>
> We run a mini
- Original Message -
> From: "Jonathan Wakely"
> To: "Marc Poulhies"
> Cc: "libstdc++" , "gcc-patches"
> , "Luc Michel"
> Sent: Wednesday, July 21, 2021 5:53:52 PM
> Subject: Re: [NEWS] libstdc++: Fix testsuite for skipping gdb tests on
> remote/non-native target
> Thanks for the patc
With the correct patch attached, sorry for the incorrect previous one !
Marc
- Original Message -
> From: "gcc-patches"
> To: "gcc-patches" , "libstdc++"
>
> Cc: "Luc Michel"
> Sent: Tuesday, July 20, 2021 4:12:16 PM
> Subject: [NEWS] libstdc++: Fix testsuite for skipping gdb tests o
This fixes an incorrect invocation of gdb on remote targets where DejaGNU would
try to run host's gdb in remote target simulator.
gdb-test skips the testing when target is remote or non native but the gdb
version check function does not.
libstdc++-v3/ChangeLog:
* testsuite/lib/gdb-test.e
