On Sat, Sep 18, 2010 at 1:25 AM, Jonathan S. Shapiro <[email protected]> wrote: > I've just discovered the first unit test that executes with different output > on two machines. Specifically, the vec-badly-typed test emits diagnostics > with different type variable names on 32-bit F13 than it does on 64-bit F11. > I haven't yet tried other 32-bit platforms.
I was able to reproduce this on x86_64 F12 with 2 builds of bitc one using -m32, using these configure options, and the attached hack to allow one to specify options for bitcc to pass to gcc ./configure LDFLAGS="-m32" CFLAGS="-m32" CXXFLAGS="-m32" BITCC_GCC_COMPILE_OPTIONS="-m32" BITCC_GCC_LINK_OPTIONS="-m32" --prefix=$HOME/bitc32 i'm guessing this isn't how we should handle it, also considering there was talk of using llvm and this makes the internal usage of gcc less than transparent, anyhow it was quick and reproduced the problem. > Anybody want to take a look a this? i have a look, but no idea if i'll get anywhere we'll find out below is what I got (32 bit first), so here neither matches the expected output which isn't what I expected. === EXPECTED OUTPUT === === EXPECTED ERROR OUTPUT === vec-badly-typed.bitc:46:7: Type Error. Expected (vector 'a24680|'a24677), Obtained (array 'a24717 5) Real Error! Exiting due to errors during Type Checking === GOT OUTPUT === === GOT ERROR ==== vec-badly-typed.bitc:46:7: Type Error. Expected (vector 'a24680|'a24677), Obtained (array 'a24713 5) Real Error! Exiting due to errors during Type Checking ================== === EXPECTED OUTPUT === === EXPECTED ERROR OUTPUT === vec-badly-typed.bitc:46:7: Type Error. Expected (vector 'a24680|'a24677), Obtained (array 'a24717 5) Real Error! Exiting due to errors during Type Checking === GOT OUTPUT === === GOT ERROR ==== vec-badly-typed.bitc:46:7: Type Error. Expected (vector 'a24720|'a24717), Obtained (array 'a24749 5) Real Error! Exiting due to errors during Type Checking
foo.diff
Description: Binary data
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
