http://sourceware.org/bugzilla/show_bug.cgi?id=13084
--- Comment #6 from Michael Zolotukhin <michael.v.zolotukhin at gmail dot com> 2012-09-23 15:17:07 UTC --- (In reply to comment #5) > (In reply to comment #4) > > If working with 64-bit values is incorrect in x32-mode, then we also need to > > fix tests from gas/i386/ilp32/x86-64.s - as they are mostly copied from > > 64-bit > > tests, they contain a lot of 64-bit values. > > Am I getting it correctly that we need to use only 32-bit values in this > > test > > too? > > Which specific tests do you want to change? We only want to issue > an error instead of silently truncating 64bit value. Other 64-bit > values are OK. Oh, I see. I just changed integer_constant function to disallow 64-bit constant in x32 mode and got fails on instructions like this: movq %rax,0xffffffffff332211 from gas/testsuite/gas/i386/ilp32/x86-64.s Now I see that it's incorrect, and we need to disallow such values only if they are going to be truncated when stored in symbol table. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
