Jean Perier ec13942e71 [flang] prevent undefined behavior in character MAXLOC folding ... When folding MAXLOC/MINLOC, the current element being compared was moved twice in row in case it became the new extremum. With numeric and logical types, it made no difference (std::move is a no-op for them), but for characters where the string storage is actually moved, it caused the new extremum to be set to the empty string, leading to wrong results. Note: I could have left the first std::move relating to logical Findloc, but it brings nothing and makes the code less auditable, so I also removed it. Differential Revision: https://reviews.llvm.org/D122590		2022-03-29 09:34:09 +02:00
..
Driver	[flang][driver] Make --version and -version consistent with clang	2022-03-28 22:53:17 +02:00
Evaluate	[flang] prevent undefined behavior in character MAXLOC folding	2022-03-29 09:34:09 +02:00
Examples	[flang][Parser] Add a node for individual sections in sections construct	2022-03-18 21:55:35 +05:30
Fir	[flang][codegen] ensure descriptor lower bounds are LBOUND compliant	2022-03-25 09:02:57 +01:00
Frontend
Lower	[flang][OpenMP] Added parallel sections translation	2022-03-29 11:16:38 +05:30
NonGtestUnit
Parser	[flang][Parser] Add a node for individual sections in sections construct	2022-03-18 21:55:35 +05:30
Preprocessing
Runtime
Semantics	[flang] Fix bogus error from assignment to CLASS(*)	2022-03-25 11:17:01 -07:00
Unit
CMakeLists.txt	[flang][NFC] Add module lowering tests	2022-03-23 17:51:09 +01:00
lit.cfg.py
lit.site.cfg.py.in