[PATCH, libstdc++ testsuite] Correct path to libatomic

Jeff Law jeffreyalaw@gmail.com
Sat Apr 24 04:12:56 GMT 2021

On 4/23/2021 6:54 PM, David Edelsohn via Gcc-patches wrote:
> Some ports require libatomic for atomic operations, at least for some
> data types and widths.  The libstdc++ testsuite previously was updated
> to link against libatomic, but the search path was hard-coded to
> something that is not always correct, and the shared library search
> path was not set.
> The search path was hard-coded to the expected location of the
> libatomic build directory relative to the libstdc++ testsuite
> directory, but if one uses parallelism when invoking the libstdc++
> testsuite, the tests are run in the "normalXX" sub-directories, for
> which the hard-coded search path is incorrect. The path also is
> incorrect for alternative multilib and tool options.
> This patch adopts the logic from gcc/testsuite/lib/atomic-dg.exp to
> search for the library and adds the logic to the libstdc++ testsuite
> libatomic seatch path code.  Previously the libstdc++ testsuite atomic
> tests failed depending on the build configuration and if a build of
> libatomic was installed in the default search path.
> Bootstrapped on powerpc-ibm-aix7.2.3.0.
> Okay to install?
> Thanks, David
> * testsuite/lib/dg-options.exp (atomic_link_flags): New.
> (add_options_for_libatomic): Use atomic_link_flags.



More information about the Libstdc++ mailing list