Displaying 4 results from an estimated 4 matches for "3dnowa".
Did you mean:
3dnow
2013 Feb 26
2
[LLVMdev] Question about intrinsic function llvm.objectsize
...vm.objectsize.i64( i8*, i1)
declare noalias i8* @malloc(i64) #1
declare void @bar1(i8*) #2
declare void @bar2(i8*) #2
declare i32 @bar3(i8*) #2
attributes #0 = { nounwind ssp uwtable "target-cpu"="core2" "target-features"="-sse4a,-avx2,-xop,-fma4,-bmi2,-3dnow,-3dnowa,-pclmul,+sse,-avx,-sse41,+ssse3,+mmx,-rtm,-sse42,-lzcnt,-f16c,-popcnt,-bmi,-aes,-fma,-rdrand,+sse2,+sse3" }
attributes #1 = { nounwind "target-cpu"="core2" "target-features"="-sse4a,-avx2,-xop,-fma4,-bmi2,-3dnow,-3dnowa,-pclmul,+sse,-avx,-sse41,+ssse3,+mmx,-r...
2013 May 17
0
[LLVMdev] How to get rid of "xxx not a recognized feature for this target" warning?
...a recognized feature for this target (ignoring feature)
'-fma4' is not a recognized feature for this target (ignoring feature)
'-bmi2' is not a recognized feature for this target (ignoring feature)
'-3dnow' is not a recognized feature for this target (ignoring feature)
'-3dnowa' is not a recognized feature for this target (ignoring feature)
'-pclmul' is not a recognized feature for this target (ignoring feature)
.....
The processor I used is generic,
def : Processor<"generic", NoItineraries, []>;
I used lldb to trace the code and didn't...
2008 Jul 20
0
[LLVMdev] Changing target features from C++
On Jul 20, 2008, at 2:59 AM, Nicolas Capens wrote:
> Hi Chris,
>
> I see. While hacking AutoDetectSubtargetFeatures() works for me for
> now, would it be useful to define an interface for X86Subtarget to
> change the features in a cleaner way? Would methods like
> disableSSEn()/enableSSEn() work or do you have another suggestion? I
> certainly want to avoid a
2008 Jul 20
3
[LLVMdev] Changing target features from C++
Hi Chris,
I see. While hacking AutoDetectSubtargetFeatures() works for me for now,
would it be useful to define an interface for X86Subtarget to change the
features in a cleaner way? Would methods like disableSSEn()/enableSSEn()
work or do you have another suggestion? I certainly want to avoid a
situation where one module uses other settings than another module.
Thanks,
Nicolas