From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/cfortran/
Date: Thu, 14 Dec 2023 04:22:19 +0000 (UTC) [thread overview]
Message-ID: <1702527640.42c3c45c2ae81d83676fa8573ee531ae21400fa1.sam@gentoo> (raw)
commit: 42c3c45c2ae81d83676fa8573ee531ae21400fa1
Author: Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Wed Dec 6 06:24:05 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Dec 14 04:20:40 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=42c3c45c
dev-lang/cfortran: add -fcommon to CFLAGS for tests
In the failing test, both the Fortran code and the C code have a symbol
called _fcb. The test expects it to be in the common section in both
objects, such that when it gets linked, they both refer to the same
symbol, such that changes on the C side to the variable are reflected on
the Fortran side and vice versa. However with -fno-common then it's
still placed in the common section in Fortran, but in C it's placed in
the BSS section, so now they refer to different objects. The linker
actually emits a warning for this, something like "alignment 1 is less
than 16".
When there are two symbols in different sections with the same name,
this is an ODR violation which is UB on all platforms.
Bug: https://bugs.gentoo.org/899452
Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Closes: https://github.com/gentoo/gentoo/pull/34143
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-lang/cfortran/cfortran-20210827.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-lang/cfortran/cfortran-20210827.ebuild b/dev-lang/cfortran/cfortran-20210827.ebuild
index feadc03d0c45..d001f52cea3b 100644
--- a/dev-lang/cfortran/cfortran-20210827.ebuild
+++ b/dev-lang/cfortran/cfortran-20210827.ebuild
@@ -41,6 +41,7 @@ src_prepare() {
src_configure() {
use sparc && append-fflags $(test-flags-FC -fno-store-merging -fno-tree-slp-vectorize) # bug 818400
+ append-cflags $(test-flags-CC -fcommon) # bug 899452
default
}
next reply other threads:[~2023-12-14 4:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 4:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-11 8:39 [gentoo-commits] repo/gentoo:master commit in: dev-lang/cfortran/ WANG Xuerui
2025-01-11 8:39 WANG Xuerui
2025-01-11 8:39 WANG Xuerui
2024-04-08 18:50 Andrew Ammerlaan
2024-03-15 6:49 Sam James
2023-03-04 11:37 Arthur Zamarin
2023-03-04 8:49 Arthur Zamarin
2023-03-04 8:49 Arthur Zamarin
2023-03-04 8:07 Arthur Zamarin
2022-06-03 12:27 Ulrich Müller
2022-05-06 7:16 Arthur Zamarin
2022-05-06 7:08 Arthur Zamarin
2021-10-16 4:25 Sam James
2021-10-12 7:10 Agostino Sarubbo
2021-10-11 5:45 Sam James
2021-10-11 4:33 Sam James
2021-10-11 4:20 Sam James
2021-08-14 23:15 Marek Szuba
2021-08-14 23:15 Marek Szuba
2021-07-21 15:39 Marek Szuba
2019-11-06 9:56 Michał Górny
2019-10-16 4:45 Matt Turner
2019-10-11 22:32 Sergei Trofimovich
2019-10-07 19:27 Sergei Trofimovich
2019-10-07 19:12 Sergei Trofimovich
2019-10-07 10:44 Agostino Sarubbo
2018-05-16 22:57 Aaron Bauman
2017-07-17 9:48 Alexis Ballier
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=1702527640.42c3c45c2ae81d83676fa8573ee531ae21400fa1.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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