[MLton] problem with strange Offset x86-codegen

Matthew Fluet fluet@cs.cornell.edu
Tue, 29 Jun 2004 13:43:02 -0400 (EDT)

> MLton raised in 23389.46 + 7081.88 (23% GC)
> x86Translate.translateChunk::x86Translate.Chunk.toX86Chunk::x86Translate.Block.toX86Blocks::x86Translate.Statement.toX86Blocks::RP(1): Pointers (pt_1178)  = OP (Cast (0x1, Pointers (pt_1567)), 0)::x86Translate.Operand.toX86Operand::toX86Operand: strange Offset: base: $0x1
> We've seen this before, but I can't remember if it's the backend's
> responsibility to make sure that offsets of immediates don't happen or
> if it's the codegen's responsibility to handle it.

"Google Archive" is your friend:
At the time, it seemed like only dead code could result in this problem,
and the right thing was for the backend to generate a call to MLton_bug.