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 libgomp/96661] configure:16984: error: unsupported system, cannot find Fortran int kind=16 Date: Tue, 28 Sep 2021 13:16:12 +0000 [thread overview] Message-ID: <bug-96661-4-gVYc5il3g4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96661-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96661 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:1f0a57bd54aed558e0167016dd980177f88f8480 commit r12-3927-g1f0a57bd54aed558e0167016dd980177f88f8480 Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue Sep 28 15:15:47 2021 +0200 libgomp: Only check for 2*sizeof(void*) int type with Fortran [PR96661] The depend type is a struct with two pointer members for C/C++ - but for Fortran OpenMP requires an integer type with kind = omp_depend_kind. Thus, libgomp's configure checks that an integer type/kind with size 2*sizeof(void*) is available. However, this integer type/kind is not needed when building without Fortran support. Thus, only check this when Fortran is enabled. libgomp/ PR libgomp/96661 * configure.ac: Only check for int-type = 2*size_t support when building with Fortran support. * configure: Regenerate.
next prev parent reply other threads:[~2021-09-28 13:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-17 16:58 [Bug libgomp/96661] New: " danglin at gcc dot gnu.org 2020-08-17 18:10 ` [Bug libgomp/96661] " burnus at gcc dot gnu.org 2020-08-17 18:28 ` dave.anglin at bell dot net 2021-09-08 22:46 ` pinskia at gcc dot gnu.org 2021-09-28 13:16 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-28 13:26 ` burnus at gcc dot gnu.org 2021-09-28 13:26 ` cvs-commit at gcc dot gnu.org 2021-11-05 16:08 ` cvs-commit at gcc dot gnu.org 2021-11-05 16:44 ` cvs-commit 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-96661-4-gVYc5il3g4@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).