public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	"Kong, Lingling" <lingling.kong@intel.com>
Cc: Binutils <binutils@sourceware.org>
Subject: RE: [PATCH 00/18] x86: new .insn directive
Date: Wed, 8 Mar 2023 08:09:37 +0000	[thread overview]
Message-ID: <SA1PR11MB59468F41723375A35723E169ECB49@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <61ad4bf3-f351-e584-1e50-7782de17d658@suse.com>

> > We will evaluate if these changes will cause any potential issues for
> > the future.
> 
> Okay, but please supply me with a time frame for this activity. It's
> not reasonable to have me sit on this kind of work (and potentially
> have to rebase it repeatedly over other work) for an extended period
> of time. Furthermore, should potential issues be found, there'll
> need to be enough detail for me to actually address these (rather
> than wait until such features would become publicly known).
> 

We have created a branch from scratch and currently under evaluating.

Lingling will give her further opinion on this. I suppose two weeks might
be enough.

Really appreciate the work and looking forward to see it happen.

Thx,
Haochen

> In the absence of a timeline I'll get v2 out soonish (I've found
> that I failed to remember to re-run the testsuite on a broader set
> of sub-targets after adding the immediate operands handling and the
> conversion of some of the existing testcases; hence some adjustments
> were needed there), and then wait like two weeks for comments of any
> kind. Should none surface, I think I can rightfully commit the whole
> lot then. (As indicated, I may commit a subset ahead of submitting
> v2, not the least to limit the volume of the re-submission. But of
> course again only unless comments surface which would need
> addressing.)
> 
> Jan

  reply	other threads:[~2023-03-08  8:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 12:54 Jan Beulich
2023-03-03 12:56 ` [PATCH 01/18] x86: introduce " Jan Beulich
2023-03-03 12:57 ` [PATCH 02/18] x86: parse VEX and alike specifiers for .insn Jan Beulich
2023-03-03 12:57 ` [PATCH 03/18] x86: parse special opcode modifiers " Jan Beulich
2023-03-03 12:58 ` [PATCH 04/18] x86: use set_rex_vrex() also for short-form handling Jan Beulich
2023-03-03 12:58 ` [PATCH 05/18] x86: move more disp processing out of md_assemble() Jan Beulich
2023-03-03 12:59 ` [PATCH 06/18] x86-64: adjust REX-prefix part of SSE2AVX test Jan Beulich
2023-03-03 13:00 ` [PATCH 07/18] x86: re-work build_modrm_byte()'s register assignment Jan Beulich
2023-03-03 13:00 ` [PATCH 08/18] x86: VexVVVV is now merely a boolean Jan Beulich
2023-03-03 13:01 ` [PATCH 09/18] x86: drop "shimm" special case template expansions Jan Beulich
2023-03-03 13:01 ` [PATCH 10/18] x86/AT&T: restrict recognition of the "absolute branch" prefix character Jan Beulich
2023-03-03 13:02 ` [PATCH 11/18] x86: process instruction operands for .insn Jan Beulich
2023-03-03 13:03 ` [PATCH 12/18] x86: decouple broadcast type and bytes fields Jan Beulich
2023-03-03 13:03 ` [PATCH 13/18] x86: handle EVEX Disp8 for .insn Jan Beulich
2023-03-03 13:04 ` [PATCH 14/18] x86: allow for multiple immediates in output_disp() Jan Beulich
2023-03-03 13:05 ` [PATCH 15/18] x86: handle immediate operands for .insn Jan Beulich
2023-03-03 13:05 ` [PATCH 16/18] x86: document .insn Jan Beulich
2023-03-03 13:06 ` [PATCH 17/18] x86: convert testcases to use .insn Jan Beulich
2023-03-03 13:06 ` [PATCH RFC 18/18] x86: .insn example - VEX-encoded instructions of original Xeon Phi Jan Beulich
2023-03-03 16:50 ` [PATCH 00/18] x86: new .insn directive H.J. Lu
2023-03-06  9:26   ` Jan Beulich
2023-03-07 20:33     ` H.J. Lu
2023-03-08  7:54       ` Jan Beulich
2023-03-08  8:09         ` Jiang, Haochen [this message]
2023-03-09  6:52           ` Kong, Lingling
2023-03-05 10:07 ` Jiang, Haochen
2023-03-06  9:01   ` 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=SA1PR11MB59468F41723375A35723E169ECB49@SA1PR11MB5946.namprd11.prod.outlook.com \
    --to=haochen.jiang@intel.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=lingling.kong@intel.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).