[cfe-dev] Warning for partially implemented options/pragmas?

Kevin Neal via cfe-dev cfe-dev at lists.llvm.org
Thu Apr 23 10:53:27 PDT 2020

I’m already working on support for target-specific handling.

I like the idea of target-specific disabling of the relevant options. I do think a warning is appropriate since this is a _correctness_ issue, and also because the options can be triggered indirectly like Cameron showed.

The target-specific parts in clang itself that need to be done are very small, and as far as I know are confined to CGBuiltins.cpp. So I don’t think that any new options need to be added for developer use. Testing is an issue, but X86 and SystemZ are in such good shape that clang tests for anything else besides builtins can test on one of those two targets.

From: Nemanja Ivanovic <nemanja.i.ibm at gmail.com>
Sent: Thursday, April 23, 2020 10:01 AM
To: cameron.mcinally at nyu.edu
Cc: Kevin Neal <Kevin.Neal at sas.com>; Clang Dev <cfe-dev at lists.llvm.org>
Subject: Re: [cfe-dev] Warning for partially implemented options/pragmas?

I think it would be quite useful to add this in the front end. The way I envision this working is that targets would specify whether they support constrained FP intrinsics. If this flag is unset, it would cause the front end to do two things:
1. Warn the user that the mode is not supported for the target
2. Ignore the option and not generate the constrained FP intrinsics

This should additionally be coupled with a temporary option for developers to use to aid in developing support for the intrinsics.
Something like: -ftrapping-math-on-unsupported-target and -frounding-math-on-unsupported-target.

On Thu, Apr 16, 2020 at 4:19 PM Cameron McInally via cfe-dev <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>> wrote:
On Thu, Apr 16, 2020 at 4:01 PM Kevin Neal via cfe-dev
<cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>> wrote:
> Bug 45329 “segfault with frounding-math” “https://bugs.llvm.org/show_bug.cgi?id=45329<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.llvm.org%2Fshow_bug.cgi%3Fid%3D45329&data=02%7C01%7CKevin.Neal%40sas.com%7Cba3a9bfacc8b4357359c08d7e78ec522%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C637232472689586464&sdata=SwcDG7o7Yj1Fj8474IhK4gJQPHV4zBLp1%2BIMAynBIyY%3D&reserved=0>” highlights that we are silently allowing people to use options that are unimplemented or only partially implemented.
> If use the -frounding-math option on a compile I expect it to work. I do not expect it to trigger an ICE, a crash, or much worse silently not work and produce wrong results.
> I propose a warning be printed so that we can avoid issues like bug 45329 in the future. And it needs to be per-target since some targets are closer to supporting this feature than others.
> Thoughts?

Thanks for bringing this up, Kevin.

We have a customer code that has been using
`-fno-unsafe-math-optimizations` for some time. That option implies
`-ftrapping-math`, which was a no-op until a few months ago. Now,
`-ftrapping-math` enables the constrained FP intrinsics, which aren't
fully supported on all targets. That behavior change looked like a
regression to the customer.

A warning would be a good short-term solution.

cfe-dev mailing list
cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20200423/04c61738/attachment.html>

More information about the cfe-dev mailing list