[flang-commits] [flang] [flang] Added a note about Fortran 202X (F202X) (PR #190627)

[Eugene Epshteyn via flang-commits]

https://github.com/eugeneepshteyn created https://github.com/llvm/llvm-project/pull/190627

Fortran 202X should no longer be used to refer to Fortran 2023 standard.

>From f7d8fc76be66ecb28abfbf51da85182beb0c9bde Mon Sep 17 00:00:00 2001
From: Eugene Epshteyn <eepshteyn at nvidia.com>
Date: Mon, 6 Apr 2026 12:23:28 -0400
Subject: [PATCH] [flang] Added a note about Fortran 202X (F202X)

Fortran 202X should no longer be used to refer to Fortran 2023 standard.
---
 flang/docs/F202X.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/flang/docs/F202X.md b/flang/docs/F202X.md
index 462f6040f9cea..68747a6cf274f 100644
--- a/flang/docs/F202X.md
+++ b/flang/docs/F202X.md
@@ -6,6 +6,12 @@
 
 -->
 
+Note: before Fortran 2023 became an official standard, it was referred to in
+flang documentation as F202X or Fortran 202X. (For this reason, Fortran standard
+post 2023 is sometimes referred to as 202Y.) At this point, 202X should no
+longer be used to refer to Fortran 2023. In this document Fortran 202X means
+Fortran 2023 draft.
+
 # A first take on Fortran 202X features for LLVM Flang
 
 I (Peter Klausler) have been studying the draft PDF of the