Re: [Nasm-devel] Instruction flags engine is merged upstream

[H. P. A. <hp...@zy...>]

On 11/24/2013 11:31 AM, Cyrill Gorcunov wrote:
> 
> Hi Peter, sorry for delay, was out. Look, I can rollback my commits
> restoring former master and move flags patches out of mainline to
> a separate tree (just one revert for all commits, it'll be easy).
> The reason I merged it into master was that -- without rebase I've
> got a number of merge problems because of new IF_ flags introduced
> into master, so the longer I stay out of mainline the harder it will
> be to port back. But again, Peter, it's not a problem to revert, just
> say a word ;)
> 

There is no reason to revert.  If it turns out to be a problem we can
just fork a new branch off 305f3cee04d1adf3f4e335c5645814f2b67e8a69 and
then re-merge later.

> Also merge here make no much sence because the commits are almost unsplittable,
> I tried to make them as simple as I can, but the change of @flags is too much
> fundamental.
> 
> As to SSE,MMX, SSE,FPU flags -- the only purpose I've had initially is to
> restore flags 1:1 as they were before avx512 changes. In future I think
> we may provide a user options to select more flags from command line
> and allow to filter instructions.
> 

That makes sense.  And yes, and the idea was that we'd be able to
enhance the CPU directive to filter instructions at some point.

	-hpa