Displaying 6 results from an estimated 6 matches for "reset_opt".
Did you mean:
set_opt
2013 Jul 25
2
[LLVMdev] Clang/LLVM 3.3 unwanted attributes being added: NoFramePointerElim
...se" "no-nans-fp-math"="false"
"unsafe-fp-math"="false" "use-soft-float"="false" }
I've tried to add options.
I've tracked the code to:
NoFramePointerElim
I've seen the description of:
./lib/Target/TargetMachine.cpp
RESET_OPTION(NoFramePointerElim, "no-frame-pointer-elim");
RESET_OPTION(NoFramePointerElimNonLeaf, "no-frame-pointer-elim-non-leaf");
RESET_OPTION(LessPreciseFPMADOption, "less-precise-fpmad");
RESET_OPTION(UnsafeFPMath, "unsafe-fp-math");
RESET_OPTION(NoInfsFP...
2013 Apr 24
0
[LLVMdev] [cfe-dev] [PROPOSAL] per-function optimization level control
...s to set the optimization level on a per function basis.
>
> http://gcc.gnu.org/onlinedocs/gcc/Function-Specific-Option-Pragmas.html
> describes the pragmas as
> #pragma GCC optimize ("string")
> #pragma GCC push_options
> #pragma GCC pop_options
> #pragma GCC reset_options
>
> Instead of imitating GCC's syntax, I think it would be better to use a
> syntax
> consistent with existing pragma clang diagnostics:
>
> #pragma clang optimize push
> #pragma clang optimize "string"
> #pragma clang optimize pop
>
Since the int...
2013 Apr 24
3
[LLVMdev] [PROPOSAL] per-function optimization level control
...mas have been added to
allow
users to set the optimization level on a per function basis.
http://gcc.gnu.org/onlinedocs/gcc/Function-Specific-Option-Pragmas.html
describes the pragmas as
#pragma GCC optimize ("string")
#pragma GCC push_options
#pragma GCC pop_options
#pragma GCC reset_options
Instead of imitating GCC's syntax, I think it would be better to use a
syntax
consistent with existing pragma clang diagnostics:
#pragma clang optimize push
#pragma clang optimize "string"
#pragma clang optimize pop
Each directive would have its own stack, which in my o...
2013 Apr 24
1
[LLVMdev] [cfe-dev] [PROPOSAL] per-function optimization level control
...vel on a per function basis.
>>
>> http://gcc.gnu.org/onlinedocs/gcc/Function-Specific-Option-Pragmas.html
>> describes the pragmas as
>> #pragma GCC optimize ("string")
>> #pragma GCC push_options
>> #pragma GCC pop_options
>> #pragma GCC reset_options
>>
>> Instead of imitating GCC's syntax, I think it would be better to use a
>> syntax
>> consistent with existing pragma clang diagnostics:
>>
>> #pragma clang optimize push
>> #pragma clang optimize "string"
>> #pragma clang...
2014 Sep 19
2
[LLVMdev] More careful treatment of floating point exceptions
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
2014 Sep 25
2
[LLVMdev] More careful treatment of floating point exceptions
...insertions(+), 8 deletions(-)
diff --git a/lib/Target/TargetMachine.cpp b/lib/Target/TargetMachine.cpp
index dcb8338..44fb521 100644
--- a/lib/Target/TargetMachine.cpp
+++ b/lib/Target/TargetMachine.cpp
@@ -68,6 +68,7 @@ void TargetMachine::resetTargetOptions(const MachineFunction *MF) const {
RESET_OPTION(NoNaNsFPMath, "no-nans-fp-math");
RESET_OPTION(UseSoftFloat, "use-soft-float");
RESET_OPTION(DisableTailCalls, "disable-tail-calls");
+ RESET_OPTION(HonorFPExceptions, "honor-fp-exceptions");
TO.MCOptions.SanitizeAddress = F->hasFnAttribute(...