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/99581] [11 Regression] internal compiler error: during RTL pass: final - void QTWTF::TCMalloc_PageHeap::scavengerThread() since r11-7526 Date: Tue, 23 Mar 2021 21:59:32 +0000 [thread overview] Message-ID: <bug-99581-4-xL421dSFby@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99581-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99581 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:be70bb5e4babdf9d3d33e8f4658452038407fa8e commit r11-7807-gbe70bb5e4babdf9d3d33e8f4658452038407fa8e Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Tue Mar 23 17:51:21 2021 -0400 [PR99581] Use relaxed memory for more aarch64 memory constraints The original patch for PR99581 resulted in GCC testsuite regression as some constraints were not declared as relaxed memory ones. This patch fixes this. gcc/ChangeLog: PR target/99581 * config/aarch64/constraints.md (Utq, UOb, UOh, UOw, UOd, UOty): Use define_relaxed_memory_constraint for them.
prev parent reply other threads:[~2021-03-23 21:59 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-13 22:16 [Bug rtl-optimization/99581] New: internal compiler error: during RTL pass: final - void QTWTF::TCMalloc_PageHeap::scavengerThread() raj.khem at gmail dot com 2021-03-15 8:39 ` [Bug target/99581] [11 Regression] " rguenth at gcc dot gnu.org 2021-03-15 13:20 ` jakub at gcc dot gnu.org 2021-03-15 13:31 ` [Bug target/99581] [11 Regression] internal compiler error: during RTL pass: final - void QTWTF::TCMalloc_PageHeap::scavengerThread() since r11-7526 jakub at gcc dot gnu.org 2021-03-15 13:39 ` jakub at gcc dot gnu.org 2021-03-15 15:26 ` vmakarov at gcc dot gnu.org 2021-03-15 22:39 ` segher at gcc dot gnu.org 2021-03-16 14:25 ` vmakarov at gcc dot gnu.org 2021-03-16 17:42 ` segher at gcc dot gnu.org 2021-03-17 11:20 ` jakub at gcc dot gnu.org 2021-03-17 18:08 ` vmakarov at gcc dot gnu.org 2021-03-17 18:12 ` vmakarov at gcc dot gnu.org 2021-03-17 18:17 ` vmakarov at gcc dot gnu.org 2021-03-17 22:23 ` vmakarov at gcc dot gnu.org 2021-03-19 12:22 ` rsandifo at gcc dot gnu.org 2021-03-19 13:00 ` segher at gcc dot gnu.org 2021-03-19 14:24 ` vmakarov at gcc dot gnu.org 2021-03-22 17:37 ` cvs-commit at gcc dot gnu.org 2021-03-23 10:39 ` jakub at gcc dot gnu.org 2021-03-23 21:59 ` cvs-commit at gcc dot gnu.org [this message]
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-99581-4-xL421dSFby@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).