On Tue, Jan 28, 2014 at 8:42 AM, Uros Bizjak <ubiz...@gmail.com> wrote: > On Tue, Jan 28, 2014 at 5:35 PM, H.J. Lu <hjl.to...@gmail.com> wrote: > >>>>> The .code16gcc directive was added to binutils back in 1999: > >> scan-asm testcase doesn't do anything useful. The only >> difference in assembly code between -m16 and -m32 is the >> .code16gcc directive All magic is done in assembler. > > The test would just pass -m16 in dg-options and scan for the above > directive. It is a simple test that -m16 works as expected. >
scan-asm doesn't work with -m32 on Linux/x86-64 with RUNTESTFLAGS="--target_board='unix{-m32}'" since -m32 is appended after any dg-options: Executing on host: /export/build/gnu/gcc-m16/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/gcc-m16/build-x86_64-linux/gcc/ /export/gnu/import/git/gcc-misc/gcc/testsuite/gcc.target/i386/m16-1.c -fno-diagnostics-show-caret -fdiagnostics-color=never -ansi -pedantic-errors -m16 -ffat-lto-objects -S -m32 -o m16-1.s (timeout = 300) Is there a way to change it? -- H.J.