llvm-6502/test/CodeGen/Generic/2009-03-29-SoftFloatVectorExtract.ll
Eric Christopher 0552d51c45 Migrate existing backends that care about software floating point
to use the information in the module rather than TargetOptions.

We've had and clang has used the use-soft-float attribute for some
time now so have the backends set a subtarget feature based on
a particular function now that subtargets are created based on
functions and function attributes.

For the one middle end soft float check go ahead and create
an overloadable TargetLowering::useSoftFloat function that
just checks the TargetSubtargetInfo in all cases.

Also remove the command line option that hard codes whether or
not soft-float is set by using the attribute for all of the
target specific test cases - for the generic just go ahead and
add the attribute in the one case that showed up.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@237079 91177308-0d34-0410-b5e6-96231b3b80d8
2015-05-12 01:26:05 +00:00

15 lines
422 B
LLVM

; RUN: llc < %s
; PR3899
@m = external global <2 x double>
define double @vector_ex() nounwind #0 {
%v = load <2 x double>, <2 x double>* @m
%x = extractelement <2 x double> %v, i32 1
ret double %x
}
; Soft-float attribute so that targets that pay attention to soft float will
; make floating point types illegal and we'll exercise the legalizer code.
attributes #0 = { "use-soft-float" = "true" }