search for: compileonly

...l of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually cause a problem (i.e., misspelled options or specifying options that conflict). Conflicting options _should_ already be handled. Detecting unknown or misspelled options is very straight forward to implement which doesn't r...

...l of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually cause a problem (i.e., misspelled options or specifying options that conflict). Conflicting options _should_ already be handled. Detecting unknown or misspelled options is very straight forward to implement which doesn't r...

...l of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually cause a problem (i.e., misspelled options or specifying options that conflict). Conflicting options _should_ already be handled. Detecting unknown or misspelled options is very straight forward to implement which doesn't r...