On 5/8/2011 6:23 PM, Jon Grant wrote:
Hello
Would it be useful to have an option to enable warning if there are
duplicates?
From my point of view, I feel that not warning duplicates may let
mistakes in the way gcc is invoked slip through, e.g. assist tracking
down these issues in makefiles.
Dave Korn wrote, On 07/05/11 16:01:
On 06/05/2011 09:00, Andreas Schwab wrote:
Ian Lance Taylor writes:
The difference is that with -E the -o option is passed to cc1, whereas
without it the -o option is passed to the assembler or the linker. The
GNU assembler and linker both have the usual Un
On 06/05/2011 09:00, Andreas Schwab wrote:
> Ian Lance Taylor writes:
>
>> The difference is that with -E the -o option is passed to cc1, whereas
>> without it the -o option is passed to the assembler or the linker. The
>> GNU assembler and linker both have the usual Unix behaviour of only
>> usi
Ian Lance Taylor writes:
> The difference is that with -E the -o option is passed to cc1, whereas
> without it the -o option is passed to the assembler or the linker. The
> GNU assembler and linker both have the usual Unix behaviour of only
> using the last -o option.
Nevertheless it might be a
Bernd Schmidt writes:
> On 05/05/2011 11:53 PM, Ian Lance Taylor wrote:
>> Jon Grant writes:
>>
>>> Is it expected that more than one -o option should be allowed by GCC
>>> on command line? The later -o option overriding earlier.
>>
>> Yes, this is expected. Most Unix utilities behave that wa
On 05/05/2011 11:53 PM, Ian Lance Taylor wrote:
> Jon Grant writes:
>
>> Is it expected that more than one -o option should be allowed by GCC
>> on command line? The later -o option overriding earlier.
>
> Yes, this is expected. Most Unix utilities behave that way: when an
> option with an argu
Jon Grant writes:
> Is it expected that more than one -o option should be allowed by GCC
> on command line? The later -o option overriding earlier.
Yes, this is expected. Most Unix utilities behave that way: when an
option with an argument is specified twice, and it only makes sense to
specify
Hello
Is it expected that more than one -o option should be allowed by GCC
on command line? The later -o option overriding earlier. I had
expected the parameter checking to detect this duplication of options.
gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3
$ gcc -W -Wall -o main main.c -omup.o
$ ls
main.c m
