Re: -print-* command-line switches misbehave or are misdocumented

2009-07-06 Thread Joe Buck
On Mon, Jul 06, 2009 at 02:35:13PM -0700, Brian O'Mahoney wrote: > Re: -print-* command-line switches misbehave or are misdocumented > > Why not just fix it, if not document the way it works, cutsie, "its a > developer feature" fools no one and just hands ammunition

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-06 Thread Brian O'Mahoney
Re: -print-* command-line switches misbehave or are misdocumented Why not just fix it, if not document the way it works, cutsie, "its a developer feature" fools no one and just hands ammunition to the anti Linux and GNU camp, they read these lists too! -- Greetings Brian

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-05 Thread Eli Zaretskii
> X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, > FORGED_RCVD_HELO autolearn=ham version=3.1.0 > From: Andreas Schwab > Cc: Dave Korn , i...@google.com, > gcc@gcc.gnu.org > Date: Sun, 05 Jul 2009 10:30:35 +0200 > > Eli Zaretskii writes: > > > Granted, I know very well

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-05 Thread Dave Korn
Eli Zaretskii wrote: >> Date: Sun, 05 Jul 2009 00:33:44 +0100 >> From: Dave Korn >> CC: Eli Zaretskii , gcc@gcc.gnu.org >> Well, the simple rule is "It can tell you where any program that gcc might >> invoke lives", isn't it? That would explain why it can locate cc1, ld and >> as, >> but not

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-05 Thread Andreas Schwab
Eli Zaretskii writes: > Granted, I know very well why it doesn't work with cpp and gcc. But I > was talking about _user_documentation_, and from the user's point of > view (as opposed to GCC programmer/hacker POV), the distinction is not > quite obvious. Either the docs should be fixed to make

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-04 Thread Eli Zaretskii
> Date: Sun, 05 Jul 2009 00:33:44 +0100 > From: Dave Korn > CC: Eli Zaretskii , gcc@gcc.gnu.org > > >> e...@fencepost:~$ gcc -print-prog-name=cpp > >> cpp > > > > Yeah, that's a clear doc bug. It used to work with "cpp", but not with > > current gcc releases. > > > >> Similarly

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-04 Thread Dave Korn
Ian Lance Taylor wrote: > Eli Zaretskii > 3. -print-prog-name: Works only for some programs; manual text >> misleading. >> >> The manual says: >> >> `-print-prog-name=PROGRAM' >> Like `-print-file-name', but searches for a program such as `cpp'. >> >> It fails to say what pro

Re: -print-* command-line switches misbehave or are misdocumented

2009-07-04 Thread Ian Lance Taylor
Eli Zaretskii writes: > Some of the -print-* command-line switches either don't work as > advertised or their documentation should be made more clear. > > All of the examples below are with the following version of GCC: > > gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5) > Copyright (C) 2006 Free

-print-* command-line switches misbehave or are misdocumented

2009-07-03 Thread Eli Zaretskii
Some of the -print-* command-line switches either don't work as advertised or their documentation should be made more clear. All of the examples below are with the following version of GCC: gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5) Copyright (C) 2006 Free Software Foundation, Inc. This