search for: usesoftfloat

...msoft-float had no effect because those attributes where not preserved in the IL. ) Then if you run llc and say -soft-float, what happens is that the code generator will compile everything as soft-float, but the value of the following will be false in XXXISelLowering getTargetMachine().Options.UseSoftFloat When the constructor for XXXISelLowering is called, TM.Options.UseSoftFloat will be true. What is interesting is that code for "make check" won't have any of the new attributes there so it will work as before. I was seeing this behavior and could not figure out how my tests could...

...because those > attributes where not preserved in the IL. ) > > Then if you run llc and say -soft-float, what happens is that the code > generator will compile everything as soft-float, but the value of the > following will be false in XXXISelLowering > getTargetMachine().Options.UseSoftFloat > > When the constructor for XXXISelLowering is called, TM.Options.UseSoftFloat > will be true. > > What is interesting is that code for "make check" won't have any of the new > attributes there so > it will work as before. > > I was seeing this behavior and...

...attributes where not preserved in the IL. ) >> >> Then if you run llc and say -soft-float, what happens is that the code >> generator will compile everything as soft-float, but the value of the >> following will be false in XXXISelLowering >> getTargetMachine().Options.UseSoftFloat >> >> When the constructor for XXXISelLowering is called, TM.Options.UseSoftFloat >> will be true. >> >> What is interesting is that code for "make check" won't have any of the new >> attributes there so >> it will work as before. >> &gt...

...-frame-pointer-elim-non-leaf"); RESET_OPTION(LessPreciseFPMADOption, "less-precise-fpmad"); RESET_OPTION(UnsafeFPMath, "unsafe-fp-math"); RESET_OPTION(NoInfsFPMath, "no-infs-fp-math"); RESET_OPTION(NoNaNsFPMath, "no-nans-fp-math"); RESET_OPTION(UseSoftFloat, "use-soft-float"); RESET_OPTION(DisableTailCalls, "disable-tail-calls"); I cannot find the code or mechanism to turn off: NoFramePointerElim No code generator has these specialized, so this is happening for all targets. Any help?

...er than ADD and SUB">; +def FeatureSaveArgs + : SubtargetFeature<"save-args", "SaveArgs", "true", + "Save register arguments on the stack.">; def FeatureSoftFloat : SubtargetFeature<"soft-float", "UseSoftFloat", "true", "Use software floating point features.">; Index: lib/Target/X86/X86FrameLowering.cpp =================================================================== --- lib/Target/X86/X86FrameLowering.cpp (revision 301500) +++ lib/Target/X86/X86Fram...

...lder, then >>>>> renamed them to AVRXXX >>>>> >>>>> Removed ARM related code, for example: >>>>> >>>>> * AEABI (eabi) >>>>> >>>>> * hasDivideInXXXMode >>>>> >>>>> * useSoftFloat (soft-float-point), hasVFP2 >>>>> >>>>> Overrided addIRTranslator, addLegalizeMachineIR, >>>>> addRegBankSelectaddGlobalInstructionSelect in AVRTargetMachine. >>>>> >>>>> Added AVRGenGlobalISel.inc to CMakeLists.txt for tabl...

Hi, I was trying to use llc with soft-float option to generate soft-float code for Sparc. But it does not work. With or without -soft-float option will generate the same code for llc. Is this still an experimental feature? -- Xun Li Computer Architecture Lab Department of Computer Science University of California, Santa Barbara

Hi everyone, vmkit requires to know the size of a jitted method before emitting the method. This allows to allocate the correct size for the method. The attached patch creates this functionality when the flag SizedMemoryCode is on. In order to implement this functionality, i had to virtualize some MachineCodeEmitter functions. Is it OK to commit the patch? Thanks, Nicolas --------------

...> +} >> + >> Index: lib/Target/TargetMachine.cpp >> =================================================================== >> --- lib/Target/TargetMachine.cpp (revision 48143) >> +++ lib/Target/TargetMachine.cpp (working copy) >> @@ -31,6 +31,7 @@ >> bool UseSoftFloat; >> bool NoZerosInBSS; >> bool ExceptionHandling; >> + bool SizedMemoryCode; >> Reloc::Model RelocationModel; >> CodeModel::Model CMModel; >> bool PerformTailCallOpt; >> Index: lib/ExecutionEngine/JIT/JITEmitter.cpp >> =====================...

...*)JumpTableBase + Offset); > +} > + > Index: lib/Target/TargetMachine.cpp > =================================================================== > --- lib/Target/TargetMachine.cpp (revision 48143) > +++ lib/Target/TargetMachine.cpp (working copy) > @@ -31,6 +31,7 @@ > bool UseSoftFloat; > bool NoZerosInBSS; > bool ExceptionHandling; > + bool SizedMemoryCode; > Reloc::Model RelocationModel; > CodeModel::Model CMModel; > bool PerformTailCallOpt; > Index: lib/ExecutionEngine/JIT/JITEmitter.cpp > =====================================================...

...>> Index: lib/Target/TargetMachine.cpp >>> =================================================================== >>> --- lib/Target/TargetMachine.cpp (revision 48143) >>> +++ lib/Target/TargetMachine.cpp (working copy) >>> @@ -31,6 +31,7 @@ >>> bool UseSoftFloat; >>> bool NoZerosInBSS; >>> bool ExceptionHandling; >>> + bool SizedMemoryCode; >>> Reloc::Model RelocationModel; >>> CodeModel::Model CMModel; >>> bool PerformTailCallOpt; >>> Index: lib/ExecutionEngine/JIT/JITEmitter.cpp >&gt...

...Target/TargetMachine.cpp >>>> =================================================================== >>>> --- lib/Target/TargetMachine.cpp (revision 48143) >>>> +++ lib/Target/TargetMachine.cpp (working copy) >>>> @@ -31,6 +31,7 @@ >>>> bool UseSoftFloat; >>>> bool NoZerosInBSS; >>>> bool ExceptionHandling; >>>> + bool SizedMemoryCode; >>>> Reloc::Model RelocationModel; >>>> CodeModel::Model CMModel; >>>> bool PerformTailCallOpt; >>>> Index: lib/ExecutionEngin...

...gt;>> ================================================================== >>>>>> --- lib/Target/TargetMachine.cpp (revision 48143) >>>>>> +++ lib/Target/TargetMachine.cpp (working copy) >>>>>> @@ -31,6 +31,7 @@ >>>>>> bool UseSoftFloat; >>>>>> bool NoZerosInBSS; >>>>>> bool ExceptionHandling; >>>>>> + bool SizedMemoryCode; >>>>>> Reloc::Model RelocationModel; >>>>>> CodeModel::Model CMModel; >>>>>> bool PerformTailCallOpt;...

...============================================================== >>>>>>> --- lib/Target/TargetMachine.cpp (revision 48143) >>>>>>> +++ lib/Target/TargetMachine.cpp (working copy) >>>>>>> @@ -31,6 +31,7 @@ >>>>>>> bool UseSoftFloat; >>>>>>> bool NoZerosInBSS; >>>>>>> bool ExceptionHandling; >>>>>>> + bool SizedMemoryCode; >>>>>>> Reloc::Model RelocationModel; >>>>>>> CodeModel::Model CMModel; >>>>>>>...

...gt; = >>>>> ================================================================== >>>>> --- lib/Target/TargetMachine.cpp (revision 48143) >>>>> +++ lib/Target/TargetMachine.cpp (working copy) >>>>> @@ -31,6 +31,7 @@ >>>>> bool UseSoftFloat; >>>>> bool NoZerosInBSS; >>>>> bool ExceptionHandling; >>>>> + bool SizedMemoryCode; >>>>> Reloc::Model RelocationModel; >>>>> CodeModel::Model CMModel; >>>>> bool PerformTailCallOpt; >>>>> In...

...============================================== >>>>>>>> --- lib/Target/TargetMachine.cpp (revision 48143) >>>>>>>> +++ lib/Target/TargetMachine.cpp (working copy) >>>>>>>> @@ -31,6 +31,7 @@ >>>>>>>> bool UseSoftFloat; >>>>>>>> bool NoZerosInBSS; >>>>>>>> bool ExceptionHandling; >>>>>>>> + bool SizedMemoryCode; >>>>>>>> Reloc::Model RelocationModel; >>>>>>>> CodeModel::Model CMModel; >>&...

Hi Sanjay, Thanks, I saw this flag and it's definitely should be considered, but it appeared to me to be static characteristic of target platform. I'm not sure how appropriate it would be to change its value from a front-end. It says "Has", while optional flag would rather say "Uses" meaning that implementation cares about floating point exceptions. Regards, Sergey

...MachineCode(false), NoFramePointerElim(false), LessPreciseFPMADOption(false), UnsafeFPMath(false), - NoInfsFPMath(false), NoNaNsFPMath(false), + NoInfsFPMath(false), NoNaNsFPMath(false), HonorFPExceptions(false), HonorSignDependentRoundingFPMathOption(false), UseSoftFloat(false), NoZerosInBSS(false), JITEmitDebugInfo(false), JITEmitDebugInfoToDisk(false), GuaranteedTailCallOpt(false), @@ -117,6 +117,11 @@ namespace llvm { /// assume the FP arithmetic arguments and results are never NaNs. unsigned NoNaNsFPMath : 1; + /// HonorFPEx...

...============================== >>>>>>>>> --- lib/Target/TargetMachine.cpp (revision 48143) >>>>>>>>> +++ lib/Target/TargetMachine.cpp (working copy) >>>>>>>>> @@ -31,6 +31,7 @@ >>>>>>>>> bool UseSoftFloat; >>>>>>>>> bool NoZerosInBSS; >>>>>>>>> bool ExceptionHandling; >>>>>>>>> + bool SizedMemoryCode; >>>>>>>>> Reloc::Model RelocationModel; >>>>>>>>> CodeModel::Mode...

On Wed, May 20, 2009 at 4:55 PM, Dan Gohman <gohman at apple.com> wrote: > Can you explain why you chose the approach of using a new pass? > I pictured removing LegalizeDAG's type legalization code would > mostly consist of finding all the places that use TLI.getTypeAction > and just deleting code for handling its Expand and Promote. Are you > anticipating something more