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: Sun, 26 Jul 2020 05:23:21 +0000	[thread overview]
Message-ID: <bug-96306-4-GDi54cuUdn@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 #9 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Initial TI support for AMDGCN has been committed, see:
https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550663.html
https://gcc.gnu.org/g:8d0b2b33748014ee57973c1d7bc9fd7706bb3da9

commit 8d0b2b33748014ee57973c1d7bc9fd7706bb3da9
Author: Andrew Stubbs <ams@codesourcery.com>
Date:   Sat Jul 25 15:02:52 2020 +0100

    amdgcn: Enable TImode

    This enables types __int128 et al for move, add, subtract, and logical
    operations.  At least shift, rotate, multiple, divide, and modulus are
broken
    so we can expect some test failures.

    This is required now because libgomp no longer builds without __int128.

    An additional patch will be required to unbreak the libgfortran build.

    gcc/ChangeLog:

            * config/gcn/gcn.c (gcn_scalar_mode_supported_p): New function.
            (TARGET_SCALAR_MODE_SUPPORTED_P): New define.

  parent reply	other threads:[~2020-07-26  5: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 [this message]
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-GDi54cuUdn@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).