public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101484] [12 Regression] trunk 20210717 ftbfs for amdgcn-amdhsa (gcn offload)
Date: Mon, 19 Jul 2021 08:27:15 +0000 [thread overview]
Message-ID: <bug-101484-4-ffjs4ZMXyK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101484-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101484
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:9f2bc5077debef2b046b6c10d38591ac324ad8b5
commit r12-2392-g9f2bc5077debef2b046b6c10d38591ac324ad8b5
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Fri Jul 16 19:12:02 2021 +0200
[gcn] Work-around libgomp 'error: array subscript 0 is outside array bounds
of â__lds struct gomp_thread * __lds[0]â [-Werror=array-bounds]' [PR101484]
... seen as of commit a110855667782dac7b674d3e328b253b3b3c919b "Correct
handling of variable offset minus constant in -Warray-bounds [PR100137]".
Awaiting a different solution, of course.
libgomp/
PR target/101484
* config/gcn/team.c: Apply '-Werror=array-bounds' work-around.
* libgomp.h [__AMDGCN__]: Likewise.
next prev parent reply other threads:[~2021-07-19 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 9:58 [Bug target/101484] New: " doko at debian dot org
2021-07-17 22:30 ` [Bug target/101484] " ams at gcc dot gnu.org
2021-07-19 6:30 ` rguenth at gcc dot gnu.org
2021-07-19 8:27 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-20 7:20 ` cvs-commit at gcc dot gnu.org
2022-01-26 13:46 ` marxin at gcc dot gnu.org
2022-01-26 13:57 ` doko at debian dot org
2022-03-21 15:54 ` tschwinge at gcc dot gnu.org
2022-03-21 16:32 ` 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-101484-4-ffjs4ZMXyK@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).