https://github.com/JDPailleux edited
https://github.com/llvm/llvm-project/pull/132409
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,4 @@
+! Check support of -m64.
+! RUN: %flang -target i386-pc-win32 -m64 -### - %s 2>&1 | FileCheck
-check-prefix=M64 %s
+
+! M64: "-triple" "{{[^-]+}}64-{{.*}}"
JDPailleux wrote:
Ok :-)
https://github.com/llvm/llvm-project/pull/132409
__
https://github.com/JDPailleux updated
https://github.com/llvm/llvm-project/pull/132409
>From 10add8793e15a4767c772556763a8c063c0eb667 Mon Sep 17 00:00:00 2001
From: Jean-Didier Pailleux
Date: Tue, 18 Mar 2025 14:51:05 +0100
Subject: [PATCH] [flang] Expose -m64 option
---
clang/include/clang/D
https://github.com/JDPailleux updated
https://github.com/llvm/llvm-project/pull/132409
>From 9522fe01070c44cdb5562b048aa94d68a8117fd1 Mon Sep 17 00:00:00 2001
From: Jean-Didier Pailleux
Date: Tue, 18 Mar 2025 14:51:05 +0100
Subject: [PATCH] [flang] Expose -m64 option
---
clang/include/clang/D
@@ -0,0 +1,6 @@
+! Check support of -m32 and -m64.
JDPailleux wrote:
Yes, of course
https://github.com/llvm/llvm-project/pull/132409
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bi
@@ -4671,14 +4671,14 @@ def EB : Flag<["-"], "EB">, Alias;
def m16 : Flag<["-"], "m16">, Group, Flags<[NoXarchOption]>,
Visibility<[ClangOption, CLOption, DXCOption]>;
def m32 : Flag<["-"], "m32">, Group, Flags<[NoXarchOption]>,
- Visibility<[ClangOption, CLOption, DXCOption
https://github.com/JDPailleux created
https://github.com/llvm/llvm-project/pull/132409
Exposes `-m32` and `-m64` options for Flang.
These options can be used to build libraries or tools (e.g. OpenBlas).
>From 404fae7c320f38f27aa666b92660341866cec0bd Mon Sep 17 00:00:00 2001
From: Jean-Didier
https://github.com/JDPailleux created
https://github.com/llvm/llvm-project/pull/130593
Hello,
Here's a proposal to support diagnostics in Flang using the `DiagnosticEngine`
provided by Clang. The goal is to have a shared diagnostic system between
Clang and Flang. A small modification has bee
JDPailleux wrote:
Hi, A PR has been created to support a diagnostic system for Flang here:
https://github.com/llvm/llvm-project/pull/130593.
I'm open to discuss and apply modifications or rework if necessary.
https://github.com/llvm/llvm-project/pull/127214
https://github.com/JDPailleux converted_to_draft
https://github.com/llvm/llvm-project/pull/130593
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
JDPailleux wrote:
> Thanks for working on this @JDPailleux.
>
> This looks like a substantial change including to parts of clang. Is it
> possible to split this into two. One PR for just the "infrastructure" and
> another for the flang-specifc warnings. This would make it easier to focus
> th
https://github.com/JDPailleux updated
https://github.com/llvm/llvm-project/pull/127214
>From 86e34cf5a7b652b0ce0158b9687543691cba7ab7 Mon Sep 17 00:00:00 2001
From: Jean-Didier Pailleux
Date: Fri, 7 Mar 2025 08:31:46 +0100
Subject: [PATCH] [flang] Add options -W[no-]unused-dummy-argument and
-
https://github.com/JDPailleux updated
https://github.com/llvm/llvm-project/pull/127214
>From 46f8e51564b14cba778893f999b3b496931d52f0 Mon Sep 17 00:00:00 2001
From: Jean-Didier Pailleux
Date: Thu, 6 Mar 2025 16:32:52 +0100
Subject: [PATCH] [flang] Add options -W[no-]unused-dummy-argument and
-
@@ -6747,8 +6747,16 @@ defm backtrace : BooleanFFlag<"backtrace">,
Group;
defm bounds_check : BooleanFFlag<"bounds-check">, Group;
defm check_array_temporaries : BooleanFFlag<"check-array-temporaries">,
Group;
defm cray_pointer : BooleanFFlag<"cray-pointer">, Group;
-defm d_l
https://github.com/JDPailleux updated
https://github.com/llvm/llvm-project/pull/127605
>From 75c8eb0bf27529c629da02b140502e7557b9be46 Mon Sep 17 00:00:00 2001
From: Jean-Didier Pailleux
Date: Tue, 18 Feb 2025 10:12:32 +0100
Subject: [PATCH] [flang][Driver] Add support of -fd-lines-as-comments a
@@ -6747,8 +6747,12 @@ defm backtrace : BooleanFFlag<"backtrace">,
Group;
defm bounds_check : BooleanFFlag<"bounds-check">, Group;
defm check_array_temporaries : BooleanFFlag<"check-array-temporaries">,
Group;
defm cray_pointer : BooleanFFlag<"cray-pointer">, Group;
-defm d_l
JDPailleux wrote:
> > If the -fd-lines-as-code option is given they are treated as if the first
> > column contained a blank.
> > If the -fd-lines-as-comments option is given, they are treated as comment
> > lines.
>
> Do the tests added in this patch check this behaviour?
Yes, if the source
https://github.com/JDPailleux updated
https://github.com/llvm/llvm-project/pull/127605
>From 2adb56dc7e3bb71a854b438a99266ab9711340ef Mon Sep 17 00:00:00 2001
From: Jean-Didier Pailleux
Date: Tue, 18 Feb 2025 10:12:32 +0100
Subject: [PATCH] [flang][Driver] Add support of -fd-lines-as-comments a
https://github.com/JDPailleux created
https://github.com/llvm/llvm-project/pull/127605
`-fd-lines-as-code` and `-fd-lines-as-comments` enables treatment for lines
beginning with `d` or `D` in fixed form sources.
Using these options in free form has no effect.
If the `-fd-lines-as-code` option
19 matches
Mail list logo
