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

[biabbas]

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

[NobodyXu]

Does VxWorks wr-cc define any macro?

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

[biabbas]

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.

[biabbas]

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

[NobodyXu]

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

[NobodyXu]

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.

[biabbas]

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.