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/99766] [11 Regression] ICE: unable to generate reloads with SVE code since r11-7807-gbe70bb5e
Date: Fri, 26 Mar 2021 01:03:21 +0000 [thread overview]
Message-ID: <bug-99766-4-FPmSZrbeCH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99766-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99766
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to rsandifo@gcc.gnu.org from comment #5)
> I wonder if the CT_RELAXED_MEMORY cases should be following
> on from CT_MEMORY rather than CT_SPECIAL_MEMORY. They're really
> normal memory constraints that just happen to accept more than
> a standard constraint.
Yes, this is the right question. The patch I am working on treats
CT_SPECIAL_MEMORY the same way as CT_MEMORY everywhere although it is enough to
do this only in lra-constraints.c.
After finishing testing I'll commit the patch. Unfortunately compiler farm
arm64 machines are too slow (2 runs of gcc tests take almost 8 hours to run
with -j8). I guess I'll fix it tomorrow.
next prev parent reply other threads:[~2021-03-26 1:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 9:47 [Bug target/99766] New: ICE: unable to generate reloads with SVE code ktkachov at gcc dot gnu.org
2021-03-25 9:47 ` [Bug target/99766] [11 Regression] " ktkachov at gcc dot gnu.org
2021-03-25 10:05 ` acoplan at gcc dot gnu.org
2021-03-25 10:06 ` acoplan at gcc dot gnu.org
2021-03-25 11:06 ` [Bug target/99766] [11 Regression] ICE: unable to generate reloads with SVE code since r11-7807-gbe70bb5e acoplan at gcc dot gnu.org
2021-03-25 15:23 ` vmakarov at gcc dot gnu.org
2021-03-25 21:14 ` rsandifo at gcc dot gnu.org
2021-03-26 1:03 ` vmakarov at gcc dot gnu.org [this message]
2021-03-26 11:57 ` acoplan at gcc dot gnu.org
2021-03-26 17:12 ` cvs-commit at gcc dot gnu.org
2021-03-26 17:27 ` vmakarov at gcc dot gnu.org
2021-03-29 9:25 ` ktkachov at gcc dot gnu.org
2022-01-01 8:48 ` cvs-commit at gcc dot gnu.org
2022-01-01 8:48 ` pinskia 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-99766-4-FPmSZrbeCH@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).