On 14 August 2017 at 00:22, Luc Van Oostenryck
<luc.vanoostenryck@xxxxxxxxx> wrote:
> On Mon, Aug 14, 2017 at 1:17 AM, Dibyendu Majumdar
> <mobile@xxxxxxxxxxxxxxx> wrote:
>>> I see here:
>>> 1) 4 errors with a bitcast wich different sizes on each side.
>>> I'm a bit surprised as the code seems to do the right thing when
>>> emitting a bitcast, I'll need to check
>>> 3) 3 errors of pointer compare with different types.
>>> It should be easy to fix.
>>>
>>
>> When you say you are seeing errors ... do you mean by running
>> sparse-llvm?
>
> yes:
> Invalid bitcast
> %R36121 = bitcast i32 %R361 to i8
> Both operands to ICmp instruction are not of the same type!
> %R378 = icmp ne i8* %R3763, %struct.lua_TValue* %R375
> Invalid bitcast
> %R10918 = bitcast i32 %R1091 to i8
> Invalid bitcast
> %R12116 = bitcast i32 %R1211 to i8
> Both operands to ICmp instruction are not of the same type!
> %R1930 = icmp eq { [184 x i8] }* %R1927, { [24 x i8] }* %ARG2
> Both operands to ICmp instruction are not of the same type!
> %R2124 = icmp eq i8* %R212221, %struct.lua_TValue* %R2121
> Invalid bitcast
> %R32617 = bitcast i32 %R3261 to i8
>
>> That won't necessarily match what I get.
>
> Yes, I realized already but I have to begin with this.
> They don't seem to be hard or conceptual bugs.
>
I was wondering if you get the same Sparse IR error I got - i.e.
pseudo that is VOID. You should be able to see this without going to
LLVM.
Regards
Dibyendu
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
