public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109458] New: invalid use 'z' operand modifier in some cases mention the 'Z' operand modifier
Date: Sun, 09 Apr 2023 17:14:15 +0000	[thread overview]
Message-ID: <bug-109458-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109458
           Summary: invalid use 'z' operand modifier in some cases mention
                    the 'Z' operand modifier
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: x86_64-*-*

The problem here is the code in i386 does this:

case 'z':
...
          if (GET_MODE_CLASS (GET_MODE (x)) == MODE_FLOAT)
            warning (0, "non-integer operand used with operand code %<z%>");
          /* FALLTHRU */

        case 'Z':

...
          else
            {
              output_operand_lossage ("invalid operand type used with "
                                      "operand code 'Z'");
              return;
            }

          output_operand_lossage ("invalid operand size for operand code 'Z'");


So the error messages for 'Z' modifier is shared with 'z' but only references
'Z'.

             reply	other threads:[~2023-04-09 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-09 17:14 pinskia at gcc dot gnu.org [this message]
2023-04-09 17:51 ` [Bug target/109458] " jakub at gcc dot gnu.org
2023-04-10  8:35 ` jakub at gcc dot gnu.org
2023-04-12 14:54 ` cvs-commit at gcc dot gnu.org
2023-04-12 14:59 ` 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-109458-4@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).