summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/expr-in-syscall/main.cpp
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2015-12-14 21:59:03 +0000
committerSanjay Patel <spatel@rotateright.com>2015-12-14 21:59:03 +0000
commitfa54acedd1fd1183143c0a7f4b77554fd8cdb1ec (patch)
tree6e7cbff67fd8ec8795d8a0cb7a4e3f1d00a92302 /lldb/packages/Python/lldbsuite/test/expression_command/expr-in-syscall/main.cpp
parent46642ffeebde1743980735e96303140f5f1a7b8b (diff)
downloadbcm5719-llvm-fa54acedd1fd1183143c0a7f4b77554fd8cdb1ec.tar.gz
bcm5719-llvm-fa54acedd1fd1183143c0a7f4b77554fd8cdb1ec.zip
add fast-math-flags to 'call' instructions (PR21290)
This patch adds optional fast-math-flags (the same that apply to fmul/fadd/fsub/fdiv/frem/fcmp) to call instructions in IR. Follow-up patches would use these flags in LibCallSimplifier, add support to clang, and extend FMF to the DAG for calls. Motivating example: %y = fmul fast float %x, %x %z = tail call float @sqrtf(float %y) We'd like to be able to optimize sqrt(x*x) into fabs(x). We do this today using a function-wide attribute for unsafe-math, but we really want to trigger on the instructions themselves: %z = tail call fast float @sqrtf(float %y) because in an LTO build it's possible that calls with fast semantics have been inlined into a function with non-fast semantics. The code changes and tests are based on the recent commits that added "notail": http://reviews.llvm.org/rL252368 and added FMF to fcmp: http://reviews.llvm.org/rL241901 Differential Revision: http://reviews.llvm.org/D14707 llvm-svn: 255555
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/expr-in-syscall/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud