public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov 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: Wed, 17 Mar 2021 22:23:28 +0000	[thread overview]
Message-ID: <bug-99581-4-ZK1uE6scA5@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 #12 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #11)
> Introducing a new memory constraint can take some time.
> 
> I guess we could switch off the offending code meanwhile because it is
> compiler crash vs unoptimal generated code choice.
> 
> I'll investigate how switching the code off affects GCC tests on aarhc64.

Unfortunately, switching off the code results in 480 GCC test failures on
aarhc64.

I'll work on introducing new memory constraint.  I hope to have a patch and
submit it for review on Friday.

  parent reply	other threads:[~2021-03-17 22:23 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 [this message]
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

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-ZK1uE6scA5@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).