VxWorks wr-cc is detected as MSVC compiler, cc adds flags "no-logo", "W4" and "--" which causes compilation issues.

Question

VxWorks wr-cc is detected as MSVC compiler, cc adds flags "no-logo", "W4" and "--" which causes compilation issues.

Closed this issue 3 months ago · 6 comments

More discussion at Zulip: https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Optimizing.20Compiler.20builtins.20causes.20build.20failure.20on.20VxWorks

Follow up of issue: rust-lang/compiler-builtins#679

Answer 1 · 2024-09-04T09:56:28.000Z

Does VxWorks wr-cc define any macro?

If it does, then we could use it to detect VxWorks wr-cc compiler.

Answer 2 · 2024-09-04T10:00:45.000Z

Does VxWorks wr-cc define any macro?

If it does, then we could use it to detect VxWorks wr-cc compiler.

Yes. It does have __VXWORKS__ macro. I'll try using this. Additionally, whenever compiling a program, cc-crate would add target=some_target. For VxWorks this behavior causes issues as each wr-cc is configured for one target.

Answer 3 · 2024-09-04T10:03:07.000Z

How does it distinguish clang from msvc on linux. On linux GNUC and clang both would be defined.

Answer 4 · 2024-09-04T10:03:57.000Z

You could put it in detect_compiler_family.c then modify tool.rs to support VxWorks wr-cc

Answer 5 · 2024-09-04T10:05:14.000Z

How does it distinguish clang from msvc on linux. On linux GNUC and clang both would be defined.

We pass -? to the compiler to detect msvc.

Answer 6 · 2024-09-04T10:08:04.000Z

Oh

How does it distinguish clang from msvc on linux. On linux GNUC and clang both would be defined.

We pass -? to the compiler to detect msvc.

Yeah. For some reason wr-cc -? returns 0.