Re: passing command-line arguments, still

2022-03-21 Thread Jonathan Wakely via Gcc
On Sat, 19 Mar 2022 at 17:10, James K. Lowden wrote: > > > 3. The "f" stands for "flag", meaning on/off. > > > > It does stand for "flag", and it looks like at some point in ancient > > history if was on/off, but then came options like -falign-loops=N. > > IME, someone made a mistake in the past,

Re: passing command-line arguments, still

2022-03-21 Thread Jonathan Wakely via Gcc
On Sat, 19 Mar 2022 at 17:53, David Edelsohn wrote: > The %{} syntax is the "Specs language" used for options processing by > GCC. It is not related to autoconf. The options processing is > handled in gcc.c. Please see the comment in gcc/gcc.cc beginning with > "The Specs Language". And https:/

Re: passing command-line arguments, still

2022-03-19 Thread David Edelsohn via Gcc
On Sat, Mar 19, 2022 at 1:11 PM James K. Lowden wrote: > > I'm collecting my remarks in one reply here, hopefully for easier > reading. I want to offer my thanks, and also my assessment of the > situation as I understand it. My critique is intended as purely > constructive. > > I understand vagu

Re: passing command-line arguments, still

2022-03-19 Thread James K. Lowden
I'm collecting my remarks in one reply here, hopefully for easier reading. I want to offer my thanks, and also my assessment of the situation as I understand it. My critique is intended as purely constructive. I understand vaguely what's going on. I'll use the -findicator-column= form because

Re: passing command-line arguments, still

2022-03-17 Thread Marek Polacek via Gcc
On Thu, Mar 17, 2022 at 12:21:36PM -0400, James K. Lowden wrote: > On Wed, 16 Mar 2022 14:45:33 -0400 > Marek Polacek wrote: > > Hi Marek, > > > Let's avoid -f-foo; use -ffoo instead, like the rest of GCC. > > Sure. I hadn't noticed the distinction. > > > > In cobol/lang.opt, I have: > > >

Re: passing command-line arguments, still

2022-03-17 Thread Joseph Myers
On Thu, 17 Mar 2022, James K. Lowden wrote: > That's good to know; at least you're not telling me it's horribly out > of date. I am puzzled, though, because AFAICT that document doen't > indicate why a leading "f" or trailing "=" controls whether or not an > option taking an argument is passed to

Re: passing command-line arguments, still

2022-03-17 Thread Jonathan Wakely via Gcc
On Thu, 17 Mar 2022 at 16:22, James K. Lowden wrote: > > On Wed, 16 Mar 2022 14:45:33 -0400 > Marek Polacek wrote: > > Hi Marek, > > > Let's avoid -f-foo; use -ffoo instead, like the rest of GCC. > > Sure. I hadn't noticed the distinction. There are no existing options of the form -f-foo, only -f

Re: passing command-line arguments, still

2022-03-17 Thread James K. Lowden
On Wed, 16 Mar 2022 14:45:33 -0400 Marek Polacek wrote: Hi Marek, > Let's avoid -f-foo; use -ffoo instead, like the rest of GCC. Sure. I hadn't noticed the distinction. > > In cobol/lang.opt, I have: > > > > indicator-column > > Make this 'findicator-column='. Does that help? Yes, with t

Re: passing command-line arguments, still

2022-03-16 Thread Marek Polacek via Gcc
On Wed, Mar 16, 2022 at 02:34:09PM -0400, James K. Lowden wrote: > [I sent this to gcc-help by mistake. I'm reposting it here in case > anyone has a suggestion. I did take dje's advice, and deleted the build > directory, except that I preserved config.status and regenerated > Makefile. The observe

passing command-line arguments, still

2022-03-16 Thread James K. Lowden
[I sent this to gcc-help by mistake. I'm reposting it here in case anyone has a suggestion. I did take dje's advice, and deleted the build directory, except that I preserved config.status and regenerated Makefile. The observed behavior remains unchanged. TIA.] https://git.symas.net:443/cobolworx