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 target/96306] gcn libgomp build broken after "libomp: Add omp_depend_kind to omp_lib.{f90,h}"
Date: Tue, 28 Sep 2021 13:23:32 +0000 [thread overview]
Message-ID: <bug-96306-4-1PjuD0UnFn@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
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #14 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Close as FIXED in GCC 12/mainline.
Support for __int128 / integer(kind=16) / TI mode is available –
and libgfortran's __int128-disable patch for GCN has been reverted.
prev parent reply other threads:[~2021-09-28 13:23 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
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 [this message]
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-1PjuD0UnFn@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).