public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 3/7] x86: move / quiesce pre-386 non-16-bit warning
Date: Fri, 19 Aug 2022 07:18:27 -0700	[thread overview]
Message-ID: <CAMe9rOoeV65hYpBt492Em867oRJFKVjxLqtCJ0GXyNJsCU3MOg@mail.gmail.com> (raw)
In-Reply-To: <0340bbbf-7177-5404-b078-f1c6be287a39@suse.com>

On Thu, Aug 18, 2022 at 11:13 PM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 18.08.2022 17:30, H.J. Lu wrote:
> > On Thu, Aug 18, 2022 at 12:21 AM Jan Beulich <jbeulich@suse.com> wrote:
> >>
> >> On 17.08.2022 21:21, H.J. Lu wrote:
> >>> On Tue, Aug 16, 2022 at 12:31 AM Jan Beulich <jbeulich@suse.com> wrote:
> >>>>
> >>>> Emitting this warning for every insn, including ones having actual
> >>>> errors, is annoying. Introduce a boolean variable to emit the warning
> >>>> just once on the first insn after .arch may have changed the things, and
> >>>> move the warning to output_insn(). (I didn't want to go as far as
> >>>> checking whether the .arch actually turned off the i386 bit, but doing
> >>>> so would be an option.)
> >>>> ---
> >>>> Otoh I wonder whether switching to a pre-386 architecture shouldn't
> >>>> automatically move to CODE_16BIT: Us emitting operand- or address-size
> >>>> prefixes violates the architecture specification. Alternatively we
> >>>> could outright reject such .arch directives when not already in 16-bit
> >>>> mode.
> >>
> >> Mind me asking - no opinion here?
> >
> > We shouldn't change the current behavior to avoid any surprises.
>
> And continue to emit non-working code. Recall that the warning message
> talks of only "addressing mode", which even I initially took to mean
> what it say, and hence being entirely bogus to emit for insns without
> memory operand (or anything else susceptible to address size setting).

If it is a real error, we should issue an error.

> I did actually try to find better wording for the warning, but
> couldn't come up with anything halfway sensible and not overly long.
>
> Jan



-- 
H.J.

  reply	other threads:[~2022-08-19 14:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  7:27 [PATCH 0/7] x86: suffix handling changes Jan Beulich
2022-08-16  7:30 ` [PATCH 1/7] x86/Intel: restrict suffix derivation Jan Beulich
2022-08-17 19:19   ` H.J. Lu
2022-08-18  6:07     ` Jan Beulich
2022-08-18 14:46       ` H.J. Lu
2022-08-19  8:19         ` Jan Beulich
2022-08-19 14:23           ` H.J. Lu
2022-08-19 14:49             ` Jan Beulich
2022-08-19 17:00               ` H.J. Lu
2022-08-22  9:34                 ` Jan Beulich
2022-08-22 14:38                   ` H.J. Lu
2022-08-16  7:30 ` [PATCH 2/7] x86: insert "no error" enumerator in i386_error enumeration Jan Beulich
2022-08-17 19:19   ` H.J. Lu
2022-08-16  7:31 ` [PATCH 3/7] x86: move / quiesce pre-386 non-16-bit warning Jan Beulich
2022-08-17 19:21   ` H.J. Lu
2022-08-18  7:21     ` Jan Beulich
2022-08-18 15:30       ` H.J. Lu
2022-08-19  6:13         ` Jan Beulich
2022-08-19 14:18           ` H.J. Lu [this message]
2022-08-16  7:32 ` [PATCH 4/7] x86: improve match_template()'s diagnostics Jan Beulich
2022-08-17 20:24   ` H.J. Lu
2022-08-18  6:14     ` Jan Beulich
2022-08-18 14:51       ` H.J. Lu
2022-08-16  7:32 ` [PATCH 5/7] x86: re-work insn/suffix recognition Jan Beulich
2022-08-17 20:29   ` H.J. Lu
2022-08-18  6:24     ` Jan Beulich
2022-08-18 15:14       ` H.J. Lu
2022-08-19  8:28         ` Jan Beulich
2022-08-23  2:00           ` H.J. Lu
2022-08-26  9:26             ` Jan Beulich
2022-08-26 18:46               ` H.J. Lu
2022-09-06  6:40                 ` Jan Beulich
2022-09-06 21:53                   ` H.J. Lu
2022-09-07  7:17                     ` Jan Beulich
2022-09-26 23:52                       ` H.J. Lu
2022-09-28 12:49                         ` Jan Beulich
2022-09-28 19:33                           ` H.J. Lu
2022-09-29  8:08                             ` Jan Beulich
2022-09-29 16:00                               ` H.J. Lu
2022-09-29 16:06                                 ` Jan Beulich
2022-09-29 16:20                                   ` H.J. Lu
2022-08-16  7:33 ` [PATCH 6/7] x86-64: further re-work insn/suffix recognition to also cover MOVSL Jan Beulich
2022-08-16  7:34 ` [PATCH 7/7] ix86: don't recognize/derive Q suffix in the common case Jan Beulich
2022-08-17 20:36   ` H.J. Lu
2022-08-18  6:29     ` Jan Beulich

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=CAMe9rOoeV65hYpBt492Em867oRJFKVjxLqtCJ0GXyNJsCU3MOg@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    /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).