From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: x86: IAMCU, L1OM, and K1OM
Date: Mon, 7 Mar 2022 06:19:25 -0800 [thread overview]
Message-ID: <CAMe9rOpCiQYBMEhJ0517knJ44zoOuguMEGRV9XjBWzdvApWFtQ@mail.gmail.com> (raw)
In-Reply-To: <e658efe6-5e43-a330-bf2b-81613ba708c8@suse.com>
On Mon, Mar 7, 2022 at 6:14 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 07.03.2022 15:09, H.J. Lu wrote:
> > On Mon, Mar 7, 2022 at 3:04 AM Jan Beulich <jbeulich@suse.com> wrote:
> >> may I ask what the status / purpose of these is? They were added years
> >> ago, but actually useful functionality has never appeared. Since I've
> >> noticed a couple of issues with the involved gas code, I'm now
> >> wondering: Should I try to make fixes, or can the logic rather be
> >> purged altogether? Even if the overhead isn't high, the presence of
> >> support for these not really usable sub-architectures is causing some
> >> extra cycles to be wasted on each and every gas invocation.
> >
> > We can deprecate L1OM and K1OM.
>
> And "deprecate" == "delete" or something less heavy?
We can delete them and make an announcement.
> > But we should keep IAMCU.
>
> IOW there's stuff to come to actually fill this?
>
What do you mean? IAMCU is used.
--
H.J.
next prev parent reply other threads:[~2022-03-07 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 11:04 Jan Beulich
2022-03-07 14:09 ` H.J. Lu
2022-03-07 14:14 ` Jan Beulich
2022-03-07 14:19 ` H.J. Lu [this message]
2022-03-07 14:24 ` Jan Beulich
2022-03-07 14:48 ` H.J. Lu
2022-03-07 14:54 ` 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=CAMe9rOpCiQYBMEhJ0517knJ44zoOuguMEGRV9XjBWzdvApWFtQ@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).