public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus 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: Mon, 17 Aug 2020 18:10:21 +0000	[thread overview]
Message-ID: <bug-96661-4-EAtnkaU9A7@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 #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to John David Anglin from comment #0)
> Guess this is because target doesn't support int128.

For "omp depend", the OpenMP spec requires that an integer type is used – and
the libgomp implementation uses two pointer [= 2*sizeof(void*)] for this.

If (as I assume) hppa64-hp-hpux11.11 uses 64bit pointers, this indeed means
that in128 is needed.

In principle, OpenMP should have used some opaque data type (user-defined
derived type). But as they didn't think of this when specifying the data type
and the best choice for the implementation in GCC was to have storage for two
pointers, I now have this problem.

I do not see an easy way out; we had the same issue before with GCN and there
the solution was to add support for int128, cf. PR 96306.

> For the most part, libgomp used to work on this target.

Probably still the case when ignoring the 'depend' feature in Fortran...

  reply	other threads:[~2020-08-17 18:10 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 ` burnus at gcc dot gnu.org [this message]
2020-08-17 18:28 ` [Bug libgomp/96661] " 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
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-EAtnkaU9A7@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).