public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96306] gcn libgomp build broken after "libomp: Add omp_depend_kind to omp_lib.{f90,h}" Date: Fri, 24 Jul 2020 12:39:35 +0000 [thread overview] Message-ID: <bug-96306-4-a1ce3rQPqH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96306-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Only by slowing down all 64-bit targets in OpenMP for Fortran by using the indirection (and make it incompatible with C/C++ too, which is even worse). I wasn't aware that gcn is BITS_PER_WORD 32 target, that makes it indeed harder, but for an offloading target that wants to support 64-bit host targets I'm afraid the extra work is needed, because user can use the kind=16 or __int128_t types in their code. It can be minimal support, e.g. just have addti3, subti3, {and,ior,xor}ti3, shifts and a few others just as expanders that lower it immediately to DImode code, and for other operations defer to library. libgcc2.[ch] I think can be convinced through macros to emit code for TImode implementation using DImode, or you have e.g. config/gcn/lib2-divmod.c that could be adjusted into lib2-divmodti.c.
next prev parent reply other threads:[~2020-07-24 12:39 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-24 7:13 [Bug target/96306] New: " tschwinge at gcc dot gnu.org 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 [this message] 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-a1ce3rQPqH@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).