[llvm-commits] [llvm] r124995 - in /llvm/trunk: lib/Target/ARM/ARMAsmPrinter.cpp lib/Target/ARM/ARMBuildAttrs.h test/CodeGen/ARM/2010-09-29-mc-asm-header-test.ll test/CodeGen/ARM/2010-10-19-mc-elf-objheader.ll

[Renato Golin]

Yes, it sets the full set of "default" features, which is by no means accurate.

When you're emitting ASM to GAS, it won't recognize all build attributes and will, unfortunately, stick to .cpu/.fpu attributes.

But, when LLVM can emit object files directly, LD will (hopefully) respect the build attributes in it.

cheers,
--renato


________________________________________
From: llvm-commits-bounces at cs.uiuc.edu [llvm-commits-bounces at cs.uiuc.edu] On Behalf Of Anton Korobeynikov [anton at korobeynikov.info]
Sent: 07 February 2011 08:39
To: Jason Kim
Cc: Jason W Kim; llvm-commits at cs.uiuc.edu
Subject: Re: [llvm-commits] [llvm] r124995 - in /llvm/trunk: lib/Target/ARM/ARMAsmPrinter.cpp lib/Target/ARM/ARMBuildAttrs.h test/CodeGen/ARM/2010-09-29-mc-asm-header-test.ll test/CodeGen/ARM/2010-10-19-mc-elf-objheader.ll

> (it didn't look like cpu name by itself sets any subtarget features on
> llvm, so I guess that needs to be coded first ?)

It definitely sets the full set of features. How else, for example,
neon codegen works with just -mcpu=cortex-a8 w/o explicit -mattr=+neon
:)


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.