From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 78F47386F434; Tue, 21 Apr 2020 13:02:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 78F47386F434
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1587474139;
 bh=fST72GjaOc56CwgJrgZHZi1E1A8GAuO3I0r/bi/ei8w=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=OltdZ3/SWhc7T0g0LWeJDO0IJ0858XsvlqS61C0gyeNd7K00yBFh8wJrzSht2izFP
 pvr6r7xaYhao57YzKK09ngvqPKlRbCRJrV2iA9N4SqFqXaHOcxVAhHvWBDqGNbb7G+
 9E3RdDW0rCV6xIOe5Ke77IiYNpLiNWOBzsuvgDSc=
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94278] [amdgcn] Offloading build failures due to
 'llvm-mc' SIGSEGV
Date: Tue, 21 Apr 2020 13:02:19 +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: unknown
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on
Message-ID: <bug-94278-4-2w2IeezfXZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94278-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94278-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 13:02:19 -0000

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

Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-04-21

--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Andrew, Julian, any insights here?

(In reply to Thomas Schwinge from comment #0)
>     Stack dump:
>     0.      Program arguments:
> [...]/install/offload-amdgcn-amdhsa/amdgcn-amdhsa/bin/as
> -triple=3Damdgcn--amdhsa -mattr=3D-code-object-v3 -mcpu=3Dfiji -filetype=
=3Dobj -o
> /tmp/ccn2bzJ1.o /tmp/cchOR6jK.mkoffload.2.s=20
>     xgcc: internal compiler error: Segmentation fault signal terminated
> program as
>     [...]
>     mkoffload: fatal error:
> [...]/build-gcc/./gcc/x86_64-pc-linux-gnu-accel-amdgcn-amdhsa-gcc returne=
d 4
> exit status
>=20
> That's with stock Ubuntu 18.04 LLVM 9 packages:
>=20
>     $ [...]/install/offload-amdgcn-amdhsa/amdgcn-amdhsa/bin/as --version
>     LLVM (http://llvm.org/):
>       LLVM version 9.0.0
>     [...]
>     $ readlink [...]/install/offload-amdgcn-amdhsa/amdgcn-amdhsa/bin/as
>     /usr/bin/llvm-mc-9
>     $ dpkg -S /usr/bin/llvm-mc-9
>     llvm-9: /usr/bin/llvm-mc-9
>     $ apt-cache policy llvm-9
>     llvm-9:
>       Installed: 1:9-2~ubuntu18.04.2
>     [...]
>=20
> As this is a problem in an external tool, are we going to declare this "n=
ot
> our problem", hoping it'll go away in a later release?  Or, do we intent =
to
> be compatible with this LLVM version, and inspect whether there maybe is =
an
> actual issue with GCC's amdgcn code generation that triggers this problem=
?=