[flang-dev] Adding a predefined preprocessor symbol __FLANG.
Richard Barton via flang-dev
flang-dev at lists.llvm.org
Thu Jul 30 00:18:38 PDT 2020
Hi all
FYI - I have proposed that we make a clean break and treat LLVM Flang as a distinct new compiler from Classic Flang rather than as just a different version of Classic Flang.
I am proposing that LLVM Flang define:
#define __flang__ 1
#define __flang_major__ "@LLVM_VERSION_MAJOR@"
#define __flang_minor__ "@LLVM_VERSION_MINOR@"
#define __flang_patchlevel__ "@LLVM_VERSION_PATCH@"
#define __flang_version__ "@LLVM_VERSION_MAJOR at .@LLVM_VERSION_MINOR at .@LLVM_VERSION_PATCH@"
rather than __FLANG.. (all caps) macros and remove __F18… macros.
Does anyone see an issue with this?
Ta
Rich
From: flang-dev <flang-dev-bounces at lists.llvm.org> On Behalf Of Steve Scalpone via flang-dev
Sent: 23 July, 2020 01:01
To: flang-dev at lists.llvm.org
Subject: [flang-dev] Adding a predefined preprocessor symbol __FLANG.
Vendors and users of classic flang may be interested in https://reviews.llvm.org/D84334, which proposes replacing the predefined preprocessor macro __F18 with __FLANG. Classic flang also defines __FLANG.
As proposed, conditionally compiled code will not be able to distinguish one flang compiler from the other.
If you have an opinion, please contribute to the review.
- Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/flang-dev/attachments/20200730/5934e25b/attachment.html>
More information about the flang-dev
mailing list