public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95730] GCN offloading ICEs after commit fe7ebef7fe4f9acb79658ed9db0749b07efc3105 "Add support for __builtin_bswap128"
Date: Wed, 17 Jun 2020 21:22:43 +0000	[thread overview]
Message-ID: <bug-95730-4-vvIOe988Qa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95730-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95730

--- Comment #1 from Andrew Stubbs <ams at gcc dot gnu.org> ---
GCN uses TImode for a few special purposes, but lacks real TImode support.

(Basically, it allows TImode loads and stores for the SLP fake vectorization,
and there's one instruction that needs two DImode values in consecutive
registers.)

Probably this is a GCN-specific issue, and we should be finding another way to
handle the quasi-128-bit values.

  reply	other threads:[~2020-06-17 21:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 20:34 [Bug target/95730] New: " tschwinge at gcc dot gnu.org
2020-06-17 21:22 ` ams at gcc dot gnu.org [this message]
2020-06-17 21:50 ` [Bug target/95730] " ebotcazou at gcc dot gnu.org
2020-06-18 13:11 ` ams at gcc dot gnu.org
2020-07-24 12:25 ` ams at gcc dot gnu.org
2020-07-24 15:04 ` ebotcazou at gcc dot gnu.org
2020-07-27 13:09 ` tschwinge at gcc dot gnu.org
2021-04-27 11:39 ` jakub at gcc dot gnu.org
2021-07-28  7:04 ` rguenth at gcc dot gnu.org
2022-04-21  7:48 ` rguenth at gcc dot gnu.org
2023-05-29 10:03 ` jakub 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-95730-4-vvIOe988Qa@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).