Re: final intermodule patch

[Alexandre Oliva <aoliva at redhat dot com>]

On Jul 14, 2003, Geoff Keating <geoffk@geoffk.org> wrote:

> Not really.  You asked for something, and the compiler gave it to you.
> If we start having -fno-i-really-meant-this-command-line options,
> where do we stop?

> $ gcc -O3 -fno-unroll-loops
> error: Are you sure you really want to switch off our wonderful loop
> error: unroller?  Use -fno-i-really-dont-want-to-unroll-loops if you do.
> $ gcc -O3 -fno-unroll-loops -fno-i-really-dont-want-to-unroll-loops
> error: Are you sure you really want to override our fine command-line
> error: checking software?  Use -fno-i-really-meant-that-command-line if you do.
> $ gcc -O3 -fno-unroll-loops -fno-i-really-dont-want-to-unroll-loops \
>   -fno-i-really-meant-that-command-line
> warning: OK, but don't say I didn't warn you.

Well, there's precedent:

[root@free root]# mkraid --force /dev/md13
 
 WARNING!
 
 NOTE: [...]
[snipped 3-paragraph (or 1-screenful) of explanations]
 You have been warned!
 
 [ If your array holds no data, or you have it all backed up, or if you
 know precisely what you are doing and you still want to proceed then use
 the --really-force (or -R) flag. ]

> *sigh* I should never have mentioned the word 'intermodule'.  I should
> have just said "looky, here's a way to compile multiple files into a
> single .o!" and let people deduce for themselves what it's good for.

-funits-at-a-time? :-)
      ^

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer