public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92469] ICE: output_operand: invalid use of register 'frame' in 7/8/9/10
Date: Mon, 04 May 2020 09:12:01 +0000	[thread overview]
Message-ID: <bug-92469-4-kN3pfCaacY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92469-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92469

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems neither accessible_reg_set nor operand_reg_set can exclude frame, because
the latter results in general_operand predicate failing for it and the former
results into the latter not being enabled either.
So, if we wanted to reject this right away, we'd have to add another hard reg
set (e.g. containing gcc internal artifical regs that shouldn't appear in asm
register specification), or a target hook that would reject such registers that
varasm.c would call.

  parent reply	other threads:[~2020-05-04  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92469-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` jakub at gcc dot gnu.org
2020-05-04  8:52 ` pinskia at gcc dot gnu.org
2020-05-04  9:12 ` jakub at gcc dot gnu.org [this message]
2020-05-05  9:07   ` Richard Sandiford
2020-05-05  9:07 ` rsandifo at gcc dot gnu.org
2020-12-08 16:38 ` ubizjak at gmail dot com
2020-12-09 12:44 ` jakub at gcc dot gnu.org
2020-12-13 16:09 ` cvs-commit at gcc dot gnu.org
2021-06-01  8:15 ` rguenth at gcc dot gnu.org
2021-06-11 20:09 ` hjl.tools at gmail dot com
2022-05-27  8:39 ` rguenth 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-92469-4-kN3pfCaacY@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).