From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1716E395C40C; Wed, 24 Jun 2020 13:16:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1716E395C40C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1593004606; bh=Pz/VXCXNWYRRvJyDnHgNj/RTQqdKUazMexCB3E4hQcI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ji8Q5L/QG1CA+CjVK//1H71+xyttr2lVoiUvqDY2oSLEU+kFmqX8UMczqDBZfDkfd 6G0SGSLqtjYM1icf1Mhte/tedIG2KZ/ZiAkQ1bnd8IN0AuiY1xYZFANITYEG6nAKry IVIgaTUoN8TvFGujmk52b8zdivVmYOx98paOFjv8= From: "ams at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95864] [11 Regression] GCN offloading execution regressions after commit f062c3f11505b70c5275e5bc0e52f3e441f8afbc "amdgcn: Switch to HSACO v3 binary format" Date: Wed, 24 Jun 2020 13:16:45 +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: 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, 24 Jun 2020 13:16:46 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95864 --- Comment #1 from Andrew Stubbs --- I'm aware of these issues. I fixed all the test failures that were definitely bugs in the HSACOv3 implementation, and the ones that remain appear to be either latent bugs uncovered by the new driver configuration, or possibly even not our problem. Of course, I could be mistaken, but I won't find out until I find time to l= ook closer.=