And there still doesn't seem to be an option to shut up the useless "warning: argument unused during ..." ones.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker what are the warnings you want to silence? Are they actually broken? I'd rather spend time fixing false warnings. -
@jfbastien The big one I want to silence and can't is the warning for having linker options in the -c line or C options in -c .s lines. -
@jfbastien Someone has an agenda of trying to make us use separate $(ASFLAGS) and $(CFLAGS) and it's not build-system-friendly. -
@jfbastien And it's contrary to all historical compiler behavior (and POSIX c99 command spec) where options not relevant to op are ignored. -
@RichFelker I see. I'm not sure what to do about this if you don't like the Mysterious Agenda. Maybe@chandlerc1024 has an opinion? -
@RichFelker@chandlerc1024 happy to help, but I'm not privy to the Agenda :-) - 2 more replies
New conversation -
-
-
@RichFelker Clang does show the warning flag in brackets after the message. -
@jckarter Oh, it just omits it on the really annoying ones that can't be turned off a all... -
@RichFelker Which ones in particular? Seems like a bug to fix. -
@jckarter The ones for unused arguments on the command line (e.g. C options when the input file is asm).
End of conversation
New conversation -
-
-
@RichFelker I get "warning: implicit conversion from 'double' to 'short' … [-Wliteral-conversion]", which does include the name.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.