public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge 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, 21 Mar 2022 15:54:31 +0000 [thread overview] Message-ID: <bug-101484-4-tJem3FmgH6@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 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |tschwinge at gcc dot gnu.org --- Comment #6 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Martin Liška from comment #4) > Can we close this as fixed? (In reply to Matthias Klose from comment #5) > yes, that builds now ..., but "fixed" only if you qualify as a proper fix the '-Wno-error=array-bounds' that I added... .-\ For the record: I thought it was worth a quick try, but Jakub's recent commit r12-7713-g32ca611c42658948f1b8883994796f35e8b4e74d "Allow (void *) 0xdeadbeef accesses without warnings [PR99578]" does not resolve this issue here.
next prev parent reply other threads:[~2022-03-21 15:54 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 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 [this message] 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-tJem3FmgH6@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: linkBe 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).