From: H. P. A. <hp...@zy...> - 2014-01-01 00:16:53
|
On 12/31/2013 03:09 PM, anonymous coward wrote: > On 12/19/13, anonymous coward <nas...@us...> wrote: >>> [nosplit eax+eax] was encoded [eax*2] previously but >>> this seems against the user's intention. >> >> Actually, it is intentional/expected behavior. >> >>> So in this case, nosplit is ignored now and [eax+eax] will be generated. >> >> See my other reply to Peter for more detail. > > This change made it into 2.11, and as a result it > is now breaking existing code for me. Please do > back it out, or add an option to control this, with > a default to the original behavior. > > An explicit NOSPLIT isn't something that NASM > can just ignore. > [nosplit eax+eax] generating [nosplit eax*2] seems like nothing so much as a bug. Seriously. What on Earth would lead you to rely on such insane behavior? -hpa |