Re: -msg_* flags for cc on osf

[Ralf Wildenhues]

Hello Peter,

* Peter O'Gorman wrote on Fri, Jul 06, 2007 at 04:47:42PM CEST:
> 
> In my opinion, unless there is a system where this patch would cause
> issues, it is much more convenient for users to not have to bracket
> their compiler flags with -Xcompiler.

Well I checked now.  You can't allow through -msg* because the system
that you would break would be just this very compiler: 4.0D's cc has
  -msg_dump
which takes no argument.  Tru 64 5.1's cxx also has
  -msg_quiet
  -msg_display_number
  -msg_display_tag

that do not take an argument.  So if you modify the patch to only allow
through
  -msg_inform | -msg_warn | -msg_error | -msg_enable | -msg_disable

with an argument then I think it should be safe.  When searched for on
the net, these strings seem to only find references to above compilers
or unrelated code snippets, but not to other compilers.

Feel free to apply then.  Note I personally would guess this to be a
marginal system though, with the number of users that benefit from not
having to use -Xcompiler to be 4, and the number of libtool users having
to take the extra bytes to be a few magnitudes higher.  Just wildly
guessing here though with no way to prove.  ;-)

Cheers, and thanks,
Ralf