RE: [PATCH 00/18] x86: new .insn directive

["Kong, Lingling" <lingling.kong@intel.com>]

It is a really good work. After checking and evaluating, I find these changes do not cause any  issues for my side.

Thanks,
Lingling
> -----Original Message-----
> From: Jiang, Haochen <haochen.jiang@intel.com>
> Sent: Wednesday, March 8, 2023 4:10 PM
> 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
> 
> > > 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