Re: gcc 3.4.1 and CPU optimization

[Zbigniew Łuszpiński <zbiggy at o2 dot pl>]

Orginal message

Big thanks for help.

> (By the way, this is off-topic on this list, which is for discussing the
> development *of* GCC. The gcc-help@gcc.gnu.org list is the one to use for
> questions about development *with* GCC.)
> 

Yes I know the aim of this list. My opening e-mail was not only made to find 
answer to my question but also to show some difficulties when compliling 
programs with gcc. That is why I send it to you, developers of gcc.

I have idea how to solve this problem. We can not fix all the scripts on this 
planet. So gcc should be fixed. I think that future version of gcc should 
have a new configuration file. For example gcc.permanent.conf. In this file 
an user could setup and configure all the user's default settings which 
should be used instead of those from command line (which are created by 
script or user). Options in such file have the highest priority and 
overwrites these one provided via command line. Such file could clean up 
parameters chaos made by scripts and users.

gcc.permanent.conf example (and proposal)
===
# This is example of new gcc.permanent.conf file. Thanks to its power you will 
# never have troubles with gcc parameters chaos
# Options with x mark are disabled
# Options without x mark are enabled
# example:
#   -enabled
# x-disabled
# The unusual x disable mark is provided to not brake syntax of gcc

# Enable specific optimization
-march=athlon-xp #enable  compilation of programs for athlon-xp

#Disable all deprecated options still active in old scripts
x-m* # disable old optimization e.g. -m386, -m486
x-mcpu # disable because -march option is in use
x-mtune # disable because -march option is in use
# End of example

This is only an idea how to solve gcc parameters confusion. It is open for 
discussion, comments, modifications, ignoring, etc.

greetings,
Zbigniew