unexpected memcmp() behavior

[regehr]

unexpected memcmp() behavior

[aqjune]

My two cents is that the memcmp'ing location is storing pointer bytes. Loading a pointer byte as an integer type (as tgt does) returns a poison value, that is the reason why the target is more poisonous, maybe.

[nunoplopes]

My two cents is that the memcmp'ing location is storing pointer bytes. Loading a pointer byte as an integer type (as tgt does) returns a poison value, that is the reason why the target is more poisonous, maybe.

Yep, that's correct. I think the bug is in memcmp; the tgt return 0 in asm mode looks correct. memcmp may not be comparing pointer bytes correctly (should compare ptr addresses).

[regehr]

sigh... I looked at the memcmp implementation but spotting a subtle flaw in it is beyond me