[BUG]: Mysterious behavior with # in command line arguments

Describe the bug

Consider the following code:

#warning "what?"
#pragma message("whattt??")

In Clang, you can silence the first diagnostic with -Wno-#warnings and the second with -Wno-#pragma-messages. Additionally, you can upgrade them into errors via -Werror=#warnings and -Werror=#pragma-messages.

However, in CE, you… can’t? Can? A bit of both? I honestly am not certain what’s going on.

Steps to reproduce

On the site, select Clang as the compiler, enter the code above.

1. Add -Wno-#warnings -Wno-#pragma-messages as the command line arguments for the compiler. Notice that the diagnostics are not suppressed. Try it again on a native client and they will be.
2. Delete the old command line arguments and add -Werror=#warnings -Werror=#pragma-messages instead. Notice that the #warning was upgraded into an error, but the #pragma message was not.
3. Scratch your head and wonder how that happens. 😃

Expected behavior

For the first step, I’d expect both diagnostics to be suppressed same as on the command line. For the second step, I’d expect both diagnostics to be upgraded to an error. This is the behavior you get from the command line.

Reproduction link

https://godbolt.org/z/68Kej8Pf7

Screenshots

Not applicable

Operating System

No response

Browser version

No response

[partouf]

quoteParse is the culprit, it turns everything after # into an object https://www.npmjs.com/package/shell-quote

it sees it as a comment

[partouf]

confirmed with a unittest its indeed the splitArguments function