Re: [PATCH] Makeconf: controlling the optimization level

2001-04-20 Thread Neal H Walfield
> This is not true. GCC always uses the last -O argument, overriding the > earlier ones. In -v, you'll see they're all passed through to cc1. > cc1 uses the last value given. Consider the following: neal@hurd:~/build/tmpfs (0)$ CFLAGS=-O1 make set -e; gcc -O -O1 -Wall -g -O3 -I. ... Thanks

Re: [PATCH] Makeconf: controlling the optimization level

2001-04-15 Thread Roland McGrath
> This is necessary as gcc selects the highest flags thus: > > # CFLAGS=-O make > > would be overridden by the default value in CFLAGS. This is not true. GCC always uses the last -O argument, overriding the earlier ones. In -v, you'll see they're all passed through to cc1. cc1 uses the

[PATCH] Makeconf: controlling the optimization level

2001-04-15 Thread Neal H Walfield
This patch adds a variable, COPTIMIZE, to Makeconf. This allows the user to easily control the level of optimization for a single file or a single module. For example: # cd libdiskfs # COPTIMIZE= make would build libdiskfs with minimal optimizations thus not eliminating variabl