[Mesa-dev] [PATCH 11/18] intel/tools/disasm: make sure that entire range is disassembled

[Rogovin, Kevin]

Your theory makes sense to me too; I suspect that something in the annotation code is the ultimate cause.


-----Original Message-----
From: Matt Turner [mailto:mattst88 at gmail.com] 
Sent: Monday, November 13, 2017 9:15 PM
To: Rogovin, Kevin <kevin.rogovin at intel.com>
Cc: mesa-dev at lists.freedesktop.org
Subject: Re: [Mesa-dev] [PATCH 11/18] intel/tools/disasm: make sure that entire range is disassembled

On Mon, Nov 13, 2017 at 5:17 AM,  <kevin.rogovin at intel.com> wrote:
> From: Kevin Rogovin <kevin.rogovin at intel.com>
>
> Without this patch, if a shader has errors, the disassembly of the 
> shader often stops after the first opcode that has errors.

I can't see anything wrong with the current code. If I'm right that
07/18 is wrong, could this be papering over the bug introduced in that patch which would have caused annotations to get lost?