search for: clenumvaln

...d > put it on LLVM website ? What you mean as "LLVM PIC documentation"? What should be included there? > Okay. We need documentation, what is the difference between DynamicNoPIC and > full PIC ? >From TargetMachine.cpp (actually this is show in llc --help): cl::values( clEnumValN(Reloc::Default, "default", "Target default relocation model"), clEnumValN(Reloc::Static, "static", "Non-relocatable code"), clEnumValN(Reloc::PIC_, "pic", "Fully relocatable, position indepen...

Anton, >> Can I ask what platform ABI's are documented other than Itanium ? > I'd bet all platform ABI are more or less documented. Right. Maybe we should collect references and do some LLVM PIC documentation and put it on LLVM website ? >> I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF >> and MachO backends. > ABI is normally induced

I've tried to do: clang++ -O3 -march=native -mtune=native \ -Rpass=loop-vectorize,slp-vectorize -Rpass-missed=loop-vectorize,slp-vectorize -Rpass-analysis=loop-vectorize,slp-vectorize \ -ffast-math -ffp-model=fast -ffp-exception-behavior=ignore -ffp-contract=fast \ -c -o vec.o vec.cc But I've got no feedback. -- Alexandre Bique

...====================================== >> --- llvm/trunk/tools/llvm-dwarfdump/llvm-dwarfdump.cpp (original) >> +++ llvm/trunk/tools/llvm-dwarfdump/llvm-dwarfdump.cpp Tue Feb 5 17:30:58 2013 >> @@ -63,6 +63,7 @@ DumpType("debug-dump", cl::init(DIDT_All >> clEnumValN(DIDT_Info, "info", ".debug_info"), >> clEnumValN(DIDT_InfoDwo, "info.dwo", ".debug_info.dwo"), >> clEnumValN(DIDT_Line, "line", ".debug_line"), >> + clEnumValN(DIDT_Frames, "frames", &...

...ault? To me it seems more secure to have all settings exactly specified. static cl::opt<llvm::FPOpFusion::FPOpFusionMode> FuseFPOps( "fp-contract", cl::desc("Enable aggressive formation of fused FP ops"), cl::init(FPOpFusion::Standard), cl::values( clEnumValN(FPOpFusion::Fast, "fast", "Fuse FP ops whenever profitable"), clEnumValN(FPOpFusion::Standard, "on", "Only fuse 'blessed' FP ops."), clEnumValN(FPOpFusion::Strict, "off", "Only fuse FP ops when the res...

> What's the current status of the test suite. After putting everything > in the llvm namespace and getting everything to link, I am getting=20 > only about 75% of the tests passing. Is this to be expected or have > I broken something? I think that you broke something, specifically the C backend. See this comment for details: http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=109#c12

Hi all, I'm trying to put together a set of rules for how the various floating point semantic modes should be handled in clang. A lot of this information will be relevant to other front ends, but the details are necessarily bound to a front end implementation so I'm framing the discussion here in terms of clang. Other front ends can choose to follow clang or not. The existence of this set