public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96306] New: gcn libgomp build broken after "libomp: Add omp_depend_kind to omp_lib.{f90,h}" Date: Fri, 24 Jul 2020 07:13:43 +0000 [thread overview] Message-ID: <bug-96306-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306 Bug ID: 96306 Summary: gcn libgomp build broken after "libomp: Add omp_depend_kind to omp_lib.{f90,h}" Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: openacc, openmp Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: tschwinge at gcc dot gnu.org CC: ams at gcc dot gnu.org, burnus at gcc dot gnu.org, jakub at gcc dot gnu.org, jules at gcc dot gnu.org Target Milestone: --- Target: gcn After commit 2631d95ae29dc6a0f5bda4af1f6595a17b1efbfd "libomp: Add omp_depend_kind to omp_lib.{f90,h}": configure: error: unsupported system, cannot find Fortran int kind=16, needed for omp_depend_kind Makefile:15426: recipe for target 'configure-target-libgomp' failed make[1]: *** [configure-target-libgomp] Error 1 Is this another instance of the "'TImode' problem" indicated in PR95730 'GCN offloading ICEs after commit fe7ebef7fe4f9acb79658ed9db0749b07efc3105 "Add support for __builtin_bswap128"', or is it something else?
next reply other threads:[~2020-07-24 7:13 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-24 7:13 tschwinge at gcc dot gnu.org [this message] 2020-07-24 7:32 ` [Bug target/96306] " jakub at gcc dot gnu.org 2020-07-24 8:13 ` burnus at gcc dot gnu.org 2020-07-24 8:37 ` ams at gcc dot gnu.org 2020-07-24 8:55 ` jakub at gcc dot gnu.org 2020-07-24 12:20 ` ams at gcc dot gnu.org 2020-07-24 12:39 ` jakub at gcc dot gnu.org 2020-07-24 13:15 ` burnus at gcc dot gnu.org 2020-07-24 15:51 ` ams at gcc dot gnu.org 2020-07-26 5:23 ` burnus at gcc dot gnu.org 2020-07-26 5:23 ` cvs-commit at gcc dot gnu.org 2020-07-27 13:07 ` tschwinge at gcc dot gnu.org 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-06-29 15:22 ` cvs-commit at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2021-09-28 13:23 ` burnus 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-96306-4@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).