public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112862] [14 regression] gfortran.dg coarray tests FAIL on macOS 12+ Date: Fri, 02 Feb 2024 09:01:13 +0000 [thread overview] Message-ID: <bug-112862-4-FR0xBGxRGE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112862-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112862 --- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:e439c7827f5c5723fdd7df9c5fac55319db204af commit r14-8732-ge439c7827f5c5723fdd7df9c5fac55319db204af Author: Iain Sandoe <iain@sandoe.co.uk> Date: Wed Jan 24 08:05:30 2024 +0000 testsuite, gfortran: Update link flags [PR112862]. The regressions here are caused by two issues: 1. In some cases there is no generated runpath for libatomic 2. In other cases there are duplicate paths. This patch simplifies the addition of the options in the main gfortran exp and removes the duplicates elewhere. We need to add options to locate libgfortran and the dependent libs libquadmath (supporting REAL*16) and libatomic (supporting operations used by coarrays). Usually '-L' options are added to point to the relevant directories for the uninstalled libraries. In cases where libraries are available as both shared and convenience some additional checks are made. For some targets -static-xxxx options are handled by specs substitution and need a '-B' option rather than '-L'. For Darwin, when embedded runpaths are in use (the default for all versions after macOS 10.11), '-B' is also needed to provide the runpath. When '-B' is used, this results in a '-L' for each path that exists (so that appending a '-L' as well is a needless duplicate). There are also cases where tools warn for duplicates, leading to spurious fails. PR target/112862 gcc/testsuite/ChangeLog: * gfortran.dg/coarray/caf.exp: Remove duplicate additions of libatomic handling. * gfortran.dg/dg.exp: Likewise. * lib/gfortran.exp: Decide on whether to present -B or -L to reference the paths to uninstalled libgfortran, libqadmath and libatomic and use that to generate the link flags.
next prev parent reply other threads:[~2024-02-02 9:01 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-05 11:40 [Bug target/112862] New: " ro at gcc dot gnu.org 2023-12-05 11:40 ` [Bug target/112862] " ro at gcc dot gnu.org 2024-01-16 17:03 ` iains at gcc dot gnu.org 2024-01-17 10:14 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-17 21:07 ` iains at gcc dot gnu.org 2024-01-17 21:07 ` iains at gcc dot gnu.org 2024-01-18 10:14 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-18 18:19 ` iains at gcc dot gnu.org 2024-01-19 14:48 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-24 8:15 ` iains at gcc dot gnu.org 2024-01-24 14:45 ` ro at gcc dot gnu.org 2024-01-24 14:48 ` iains at gcc dot gnu.org 2024-01-24 15:01 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-24 15:33 ` iains at gcc dot gnu.org 2024-01-28 15:14 ` iains at gcc dot gnu.org 2024-02-02 9:01 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-02 9:04 ` iains at gcc dot gnu.org 2024-02-10 15:22 ` [Bug target/112862] " iains at gcc dot gnu.org 2024-05-07 7:42 ` rguenth at gcc dot gnu.org
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=bug-112862-4-FR0xBGxRGE@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).