Bug 13680 - gcc ignores illegal double-dash command line options
Summary: gcc ignores illegal double-dash command line options
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: driver (show other bugs)
Version: 3.4.0
: P2 minor
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-14 11:12 UTC by Mike Lange
Modified: 2005-07-23 22:49 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Lange 2004-01-14 11:12:10 UTC 
> gcc --y 
gcc: no input files

> gcc -y 
gcc: unrecognized option `-y'
gcc: no input files
Comment 1 Andreas Schwab 2004-01-14 16:21:43 UTC 
"--foo" is equivalent to "-ffoo".  The meaning of -f options depends on the 
language to compile, which depends on the name of the input file.
Comment 2 Andrew Pinski 2004-01-14 17:37:53 UTC 
Invalid as  Andreas said already.
Comment 3 Mike Lange 2004-01-14 18:22:04 UTC 
(In reply to comment #1)
> "--foo" is equivalent to "-ffoo".  The meaning of -f options depends on the 
> language to compile, which depends on the name of the input file. 

gcc -c test.c -o test.o
gcc --y --blahhh -fuhhhh test.o -o test

[test.c is some valid c-code]

So, I'd say gcc ignores illegal double-dash(or -f..) command line options *if* 
the input file is named test.o!
Comment 4 Andrew Pinski 2004-01-14 18:24:53 UTC 
the -f* flags (aka --*) get only passed to the real compiles, when the input file *.o that file gets 
passed to linker so the -f* flags do not get passed on.
Comment 5 Mike Lange 2004-01-14 18:51:03 UTC 
So, this bug is impossible to fix, right?