<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm-project.git/clang/test/CodeGen/fp-floatcontrol-stack.cpp, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/'/>
<entry>
<title>Remove FiniteMathOnly  and use only NoHonorINFs and NoHonorNANs. (#97342)</title>
<updated>2024-07-26T12:16:38+00:00</updated>
<author>
<name>Zahira Ammarguellat</name>
<email>zahira.ammarguellat@intel.com</email>
</author>
<published>2024-07-26T12:16:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=c9c91f59c318e28d884e5762f303348ba5724d21'/>
<id>c9c91f59c318e28d884e5762f303348ba5724d21</id>
<content type='text'>
Currently `__FINITE_MATH_ONLY__` is set when `FiniteMathOnly`. And
`FiniteMathOnly` is set when `NoHonorInfs` &amp;&amp; `NoHonorNans` is true. But
what happens one of the latter flags is false?
To avoid potential inconsistencies, the internal option `FiniteMathOnly`
is removed option and the macro `__FINITE_MATH_ONLY__` is set when
`NoHonorInfs` &amp;&amp; `NoHonorNans`.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently `__FINITE_MATH_ONLY__` is set when `FiniteMathOnly`. And
`FiniteMathOnly` is set when `NoHonorInfs` &amp;&amp; `NoHonorNans` is true. But
what happens one of the latter flags is false?
To avoid potential inconsistencies, the internal option `FiniteMathOnly`
is removed option and the macro `__FINITE_MATH_ONLY__` is set when
`NoHonorInfs` &amp;&amp; `NoHonorNans`.</pre>
</div>
</content>
</entry>
<entry>
<title>[clang][CodeGen] Ensure consistent `mustprogress` attribute emission</title>
<updated>2023-11-11T08:43:03+00:00</updated>
<author>
<name>Antonio Frighetto</name>
<email>me@antoniofrighetto.com</email>
</author>
<published>2023-11-06T22:20:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=970bf07d0b184c7ec356ae8f47b193a5e3ff0309'/>
<id>970bf07d0b184c7ec356ae8f47b193a5e3ff0309</id>
<content type='text'>
Emission of `mustprogress` attribute previously occurred only within
`EmitFunctionBody`, after generating the function body. Other routines
for function body creation may lack the attribute, potentially leading
to suboptimal optimizations later in the pipeline. Attribute emission
is now anticipated prior to generating the function body.

Fixes: https://github.com/llvm/llvm-project/issues/69833.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Emission of `mustprogress` attribute previously occurred only within
`EmitFunctionBody`, after generating the function body. Other routines
for function body creation may lack the attribute, potentially leading
to suboptimal optimizations later in the pipeline. Attribute emission
is now anticipated prior to generating the function body.

Fixes: https://github.com/llvm/llvm-project/issues/69833.
</pre>
</div>
</content>
</entry>
<entry>
<title>clang: Stop emitting "strictfp"</title>
<updated>2023-07-07T19:28:21+00:00</updated>
<author>
<name>Matt Arsenault</name>
<email>Matthew.Arsenault@amd.com</email>
</author>
<published>2022-12-07T23:50:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=42d4c85ca83f25f993444fb5bbaa58525f724991'/>
<id>42d4c85ca83f25f993444fb5bbaa58525f724991</id>
<content type='text'>
The attribute is a proper enum attribute, strictfp. We were getting
strictfp and "strictfp" set on every function with
-fexperimental-strict-floating-point.

https://reviews.llvm.org/D139629
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The attribute is a proper enum attribute, strictfp. We were getting
strictfp and "strictfp" set on every function with
-fexperimental-strict-floating-point.

https://reviews.llvm.org/D139629
</pre>
</div>
</content>
</entry>
<entry>
<title>[clang][patch][FPEnv] Fix syntax errors in pragma float_control test</title>
<updated>2021-07-30T13:59:45+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2021-07-30T13:59:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=0a175ad445f095caf59f7175fbc035464919b7a3'/>
<id>0a175ad445f095caf59f7175fbc035464919b7a3</id>
<content type='text'>
In a post-commit message to https://reviews.llvm.org/D102343
@MaskRay pointed out syntax errors in one of the test cases. This
patch fixes those problems, I had forgotten the colon after the CHECK- strings.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In a post-commit message to https://reviews.llvm.org/D102343
@MaskRay pointed out syntax errors in one of the test cases. This
patch fixes those problems, I had forgotten the colon after the CHECK- strings.
</pre>
</div>
</content>
</entry>
<entry>
<title>[clang][patch][FPEnv] Make initialization of C++ globals strictfp aware</title>
<updated>2021-07-29T16:02:37+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2021-07-29T16:02:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=bc5b5ea037dbadd281c59248ae9d2742b51c69ed'/>
<id>bc5b5ea037dbadd281c59248ae9d2742b51c69ed</id>
<content type='text'>
@kpn pointed out that the global variable initialization functions didn't
have the "strictfp" metadata set correctly, and @rjmccall said that there
was buggy code in SetFPModel and StartFunction, this patch is to solve
those problems. When Sema creates a FunctionDecl, it sets the
FunctionDeclBits.UsesFPIntrin to "true" if the lexical FP settings
(i.e. a combination of command line options and #pragma float_control
settings) correspond to ConstrainedFP mode. That bit is used when CodeGen
starts codegen for a llvm function, and it translates into the
"strictfp" function attribute. See bugs.llvm.org/show_bug.cgi?id=44571

Reviewed By: Aaron Ballman

Differential Revision: https://reviews.llvm.org/D102343
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
@kpn pointed out that the global variable initialization functions didn't
have the "strictfp" metadata set correctly, and @rjmccall said that there
was buggy code in SetFPModel and StartFunction, this patch is to solve
those problems. When Sema creates a FunctionDecl, it sets the
FunctionDeclBits.UsesFPIntrin to "true" if the lexical FP settings
(i.e. a combination of command line options and #pragma float_control
settings) correspond to ConstrainedFP mode. That bit is used when CodeGen
starts codegen for a llvm function, and it translates into the
"strictfp" function attribute. See bugs.llvm.org/show_bug.cgi?id=44571

Reviewed By: Aaron Ballman

Differential Revision: https://reviews.llvm.org/D102343
</pre>
</div>
</content>
</entry>
<entry>
<title>[clang][patch] Solve PR49479, File scope fp pragma should propagate to functions nested in struct, and initialization expressions</title>
<updated>2021-03-15T16:15:20+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2021-03-15T14:06:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=33b1f3f42cb9fc4fed9501ed49e4805f134e7a1b'/>
<id>33b1f3f42cb9fc4fed9501ed49e4805f134e7a1b</id>
<content type='text'>
Previously, the CurFPFeatures state was set to command line settings before
semantic analysis of the nested member functions and initialization
expressions, that's not correct, it should use the pragma state which
is in effect at the lexical position.

Reviewed By: Erich Keane, Aaron Ballman

Differential Revision: https://reviews.llvm.org/D98211
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously, the CurFPFeatures state was set to command line settings before
semantic analysis of the nested member functions and initialization
expressions, that's not correct, it should use the pragma state which
is in effect at the lexical position.

Reviewed By: Erich Keane, Aaron Ballman

Differential Revision: https://reviews.llvm.org/D98211
</pre>
</div>
</content>
</entry>
<entry>
<title>[clang] FastMathFlags.allowContract should be initialized only from FPFeatures.allowFPContractAcrossStatement</title>
<updated>2020-05-20T13:19:10+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2020-05-15T14:30:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=827be690dce158924924a70fda79b35a9d7ad1cc'/>
<id>827be690dce158924924a70fda79b35a9d7ad1cc</id>
<content type='text'>
Summary: Fix bug introduced in D72841 adding support for pragma float_control

Reviewers: rjmccall, Anastasia

Differential Revision: https://reviews.llvm.org/D79903
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary: Fix bug introduced in D72841 adding support for pragma float_control

Reviewers: rjmccall, Anastasia

Differential Revision: https://reviews.llvm.org/D79903
</pre>
</div>
</content>
</entry>
<entry>
<title>Reapply "Add support for #pragma float_control" with buildbot fixes</title>
<updated>2020-05-04T12:51:25+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2020-05-01T17:32:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=f5360d4bb3376347479d86547d21b95d80be786d'/>
<id>f5360d4bb3376347479d86547d21b95d80be786d</id>
<content type='text'>
Add support for #pragma float_control

Reviewers: rjmccall, erichkeane, sepavloff

Differential Revision: https://reviews.llvm.org/D72841

This reverts commit fce82c0ed310174fe48e2402ac731b6340098389.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add support for #pragma float_control

Reviewers: rjmccall, erichkeane, sepavloff

Differential Revision: https://reviews.llvm.org/D72841

This reverts commit fce82c0ed310174fe48e2402ac731b6340098389.
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "Reapply "Add support for #pragma float_control" with improvements to"</title>
<updated>2020-05-01T17:31:09+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2020-05-01T17:31:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=fce82c0ed310174fe48e2402ac731b6340098389'/>
<id>fce82c0ed310174fe48e2402ac731b6340098389</id>
<content type='text'>
This reverts commit 69aacaf699922ffe0450f567e21208c10c84731f.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 69aacaf699922ffe0450f567e21208c10c84731f.
</pre>
</div>
</content>
</entry>
<entry>
<title>Reapply "Add support for #pragma float_control" with improvements to</title>
<updated>2020-05-01T17:03:30+00:00</updated>
<author>
<name>Melanie Blower</name>
<email>melanie.blower@intel.com</email>
</author>
<published>2020-05-01T16:26:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=69aacaf699922ffe0450f567e21208c10c84731f'/>
<id>69aacaf699922ffe0450f567e21208c10c84731f</id>
<content type='text'>
test cases
Add support for #pragma float_control

Reviewers: rjmccall, erichkeane, sepavloff

Differential Revision: https://reviews.llvm.org/D72841

This reverts commit 85dc033caccaa6ab919d57f9759290be41240146, and makes
corrections to the test cases that failed on buildbots.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
test cases
Add support for #pragma float_control

Reviewers: rjmccall, erichkeane, sepavloff

Differential Revision: https://reviews.llvm.org/D72841

This reverts commit 85dc033caccaa6ab919d57f9759290be41240146, and makes
corrections to the test cases that failed on buildbots.
</pre>
</div>
</content>
</entry>
</feed>
