It turns out that due to the perversities of the current PNaCl compilation the .o generation actually happens ... in the link stage (!)
It turns out that due to the perversities of the current PNaCl compilation
the .o generation actually happens ... in the link stage (!)

So in order to test MC/.o, the linker flag to driver.py needs to have the
--pnacl-force-mc-direct flag for non-PIC cases.

Note that a few tests (barebones) override the linker flags so they aren't
using MC/.o, but the majority of the cases are.

PIC tests as well as SPEC2k are still run using the old .bc -> .s -> .o path.

BUG=http://code.google.com/p/nativeclient/issues/detail?id=1588
TEST=tools/llvm/utman.sh test-arm
TEST=tools/llvm/utman.sh test-arm-pic
Review URL: http://codereview.chromium.org/6837008

git-svn-id: 721b910a23eff8a86f00c8fd261a7587cddf18f8@4852 fcba33aa-ac0c-11dd-b9e7-8d5594d729c2

nacl-webkit/native_client,sbc100/native_client,sbc100/native_client,nacl-webkit/native_client,sbc100/native_client,nacl-webkit/native_client,nacl-webkit/native_client,sbc100/native_client,sbc100/native_client,nacl-webkit/native_client,sbc100/native_client