From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 30DAC3947C3D; Wed, 17 Jun 2020 21:22:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 30DAC3947C3D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1592428963; bh=QHk5A+8y0NnO1VIAO24C/zEMbcRywY3nIu96pkNQ1BY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=iJtjaj2PrSGGmzNGbce7qf6SfyrQIWR+X0nswqN8+gPeyU4gcAA6Y+vy69ZioCM/c Dox/lZVsjsDzT2WmzIcGYKRNkwfO1QugJvaVxpV4nbJciBahJHsi2vTBBDVDWoYhs+ Brl420o7hGIF9+MoQ5jcZz1cHTKKhG23Yp778/V8= From: "ams at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: openacc, openmp X-Bugzilla-Severity: normal X-Bugzilla-Who: ams at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ams at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2020 21:22:43 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95730 --- Comment #1 from Andrew Stubbs --- GCN uses TImode for a few special purposes, but lacks real TImode support. (Basically, it allows TImode loads and stores for the SLP fake vectorizatio= n, 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.=