From: "H.J. Lu" <hjl.tools@gmail.com>
To: Michael Matz <matz@suse.de>
Cc: Jan Beulich <jbeulich@suse.com>, binutils@sourceware.org
Subject: Re: [PATCH] x86: Warn .insn instruction with length > 15 bytes
Date: Tue, 6 Feb 2024 06:49:21 -0800 [thread overview]
Message-ID: <CAMe9rOrnqZNkUpOmvYNJDaJxM8zusAW6nMEjHdHdp=sBgDw+sw@mail.gmail.com> (raw)
In-Reply-To: <533a896f-8eec-b73b-cb18-26240ad822fc@suse.de>
On Tue, Feb 6, 2024 at 6:43 AM Michael Matz <matz@suse.de> wrote:
>
> Hello,
>
> On Tue, 6 Feb 2024, H.J. Lu wrote:
>
> > > > We issue a warning when something is wrong in input, but still manage
> > > > to generate an instruction. This is an error case.
> > >
> > > I disagree. It was a warning until you changed it (without me really
> > > agreeing), and some hypothetical vendor could come and lift the limit,
> > > on precisely the basis that there are legal encodings exceeding it. I'm
> > > okay if this can be forced to be an error, but I continue to think that
> > > it ought to be a warning only by default.
> > >
> >
> > It is an error on both Intel and AMD processors. There is no
> > valid reason not to be an error at the moment.
>
> Jan gave you one. I would prefer for the assembler to not be anally
That is not a valid reason. There is no such processor in the foreseeable
future.
> retentive. An error that can be disabled is completely enough for this.
>
> (I would wish for a general demote-all-errors-to-warnings option, like we
> already have a promote-all-warnings-to-errors; but lacking this an option
> to merely disable "errors" for avoiding specific random hardware behaviour
> would be fine as well)
>
>
> Ciao,
> Michael.
--
H.J.
next prev parent reply other threads:[~2024-02-06 14:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 20:00 H.J. Lu
2024-02-06 8:19 ` Jan Beulich
2024-02-06 11:36 ` H.J. Lu
2024-02-06 11:41 ` Jan Beulich
2024-02-06 12:26 ` H.J. Lu
2024-02-06 14:43 ` Michael Matz
2024-02-06 14:49 ` H.J. Lu [this message]
2024-02-06 15:04 ` Michael Matz
2024-02-06 15:34 ` H.J. Lu
2024-02-06 15:48 ` Michael Matz
2024-02-06 16:28 ` H.J. Lu
2024-02-06 17:05 ` Jan Beulich
2024-02-06 18:06 ` H.J. Lu
2024-02-07 7:51 ` Jan Beulich
2024-02-07 15:24 ` H.J. Lu
2024-02-07 15:32 ` Jan Beulich
2024-02-07 16:53 ` H.J. Lu
2024-02-07 16:59 ` Jan Beulich
2024-02-07 17:03 ` H.J. Lu
2024-02-08 4:09 ` Jiang, Haochen
2024-02-08 4:47 ` Hongyu Wang
2024-02-08 8:15 ` Jan Beulich
2024-02-08 8:23 ` Jan Beulich
2024-02-08 11:38 ` H.J. Lu
2024-02-08 6:26 ` Sunil Pandey
2024-02-08 6:41 ` Cui, Lili
2024-02-08 8:18 ` Jan Beulich
2024-02-08 11:31 ` H.J. Lu
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='CAMe9rOrnqZNkUpOmvYNJDaJxM8zusAW6nMEjHdHdp=sBgDw+sw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=matz@suse.de \
/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).