[all-commits] [llvm/llvm-project] b2048d: [Clang] [Driver] Support `-fjmc` for `*-windows-ms...

Max Winkler via All-commits all-commits at lists.llvm.org
Wed Sep 4 18:53:00 PDT 2024


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: b2048de55ea934b70902864767b0cc8dfada8be0
      https://github.com/llvm/llvm-project/commit/b2048de55ea934b70902864767b0cc8dfada8be0
  Author: Max Winkler <max.enrico.winkler at gmail.com>
  Date:   2024-09-04 (Wed, 04 Sep 2024)

  Changed paths:
    M clang/lib/Driver/ToolChains/Clang.cpp
    M clang/test/Driver/clang_f_opts.c

  Log Message:
  -----------
  [Clang] [Driver] Support `-fjmc` for `*-windows-msvc` target in non cl driver modes (#107177)

Allow `-fjmc` to be used if the target triple is targeting msvc,
`*-windows-msvc`, irrelevant of the driver mode used.

In general the driver mode shouldn't control the target triple.

Also in our custom build system I am trying to just treat clang as
clang. This is because while the `cl` driver mode emulates msvc
interface quite well there are still a lot of operations that are just
clang specific.
The optimization modes do not map directly from msvc to clang.
Warnings do not map from msvc to clang.
Instead of wrapping options with `/clang:` when targeting `clang-cl.exe`
it is just easier to target the clang driver always irrelevant of the
target triple.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list