From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 0/6] x86: drop L1OM/K1OM from gas plus associated tidying
Date: Wed, 16 Mar 2022 10:11:27 -0700 [thread overview]
Message-ID: <CAMe9rOo9ROeGLvmuc1Hks-8VWGLrThz6zZg0vV2hW1mG1+-twA@mail.gmail.com> (raw)
In-Reply-To: <93cecdf2-b805-4508-9e34-89fd0011ccc9@suse.com>
On Wed, Mar 16, 2022 at 1:42 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> It was the bugs / shortcomings dealt with here as a "side effect"
> which made me raise the question of the utility of having the
> rudimentary support for the two sub-architectures. Oddly enough
> some of the bugs need fixing _before_ removing the support, or else
> IAMCU would regress. Furthermore a new IAMCU test can be put in
> place only _after_ removing the support.
>
> 1: assorted IAMCU CPU checking fixes
> 2: drop L1OM/K1OM support from gas
> 3: add another IAMCU testcase
> 4: unify CPU flag on/off processing
> 5: never set i386_cpu_flags' "unused" field
> 6: don't accept base architectures as extensions
>
OK to all.
Can you also remove L1OM/K1OM from ld and binutils?
Thanks.
--
H.J.
next prev parent reply other threads:[~2022-03-16 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 8:42 Jan Beulich
2022-03-16 8:45 ` [PATCH 1/6] x86: assorted IAMCU CPU checking fixes Jan Beulich
2022-03-16 8:46 ` [PATCH 2/6] x86: drop L1OM/K1OM support from gas Jan Beulich
2022-03-16 8:46 ` [PATCH 3/6] x86: add another IAMCU testcase Jan Beulich
2022-05-18 17:46 ` H.J. Lu
2022-03-16 8:47 ` [PATCH 4/6] x86: unify CPU flag on/off processing Jan Beulich
2022-03-16 8:48 ` [PATCH 5/6] x86: never set i386_cpu_flags' "unused" field Jan Beulich
2022-03-16 8:48 ` [PATCH 6/6] x86: don't accept base architectures as extensions Jan Beulich
2022-03-16 17:11 ` H.J. Lu [this message]
2022-03-17 8:32 ` [PATCH 0/6] x86: drop L1OM/K1OM from gas plus associated tidying Jan Beulich
2022-03-17 15:11 ` 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=CAMe9rOo9ROeGLvmuc1Hks-8VWGLrThz6zZg0vV2hW1mG1+-twA@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).