diff options
| author | Martin Storsjö <martin@martin.st> | 2023-10-01 23:42:16 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-01 23:42:16 +0300 |
| commit | e39de2b8862ae43459324da84279366997265078 (patch) | |
| tree | 0a31244a7a01bfab4a7cf82469868df331d66a51 /flang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 95f4b2a70850b5e6ab83ec21af3fe5246cac0675 (diff) | |
| download | llvm-e39de2b8862ae43459324da84279366997265078.zip llvm-e39de2b8862ae43459324da84279366997265078.tar.gz llvm-e39de2b8862ae43459324da84279366997265078.tar.bz2 | |
[clang] [MinGW] Tolerate mingw specific linker options during compilation (#67891)
Prior to 591c4b64b3650884c2c68eb47d755ebb62981b99, the mingw specific
linker options -mthreads, -mconsole, -mwindows and -mdll would be
tolerated also at compile time, but generating a warning about being
unused.
After that commit, they were marked as target specific, which means that
it's an error if they're unused (which would consider them used for the
wrong target). These specific options are only relevant when linking,
but we want to tolerate them at compile time too, like before.
This was fixed for -mthreads in
a79995ca6004082774a87f7a58ab6be5343364b7, while the other options didn't
seem to be commonly used during compilation.
After the 17.x release, we've got more reports about this actually being
an issue, in #64464. Therefore, apply the same fix for them; marking
them as tolerated for mingw targets during compilation, even if they're
unused. Also add a testcase for -mthreads which was already handled.
Thus, this fixes #64464.
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions