Snapshot gcc-4.1-20060512 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20060512/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.1 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On Fri, May 12, 2006 at 08:40:07PM +0200, Etienne Lorrain wrote:
> But when I tried (replacing in Gujin some calll by lcallw based on which
> function
> is called) it did not work as I expected it. For instance, -fno-function-cse
> seem
> ignored here:
What are you expecting to happen here?
Hello,
the docs for "-fno-function-cse" says:
`-fno-function-cse'
Do not put function addresses in registers; make each instruction
that calls a constant function contain the function's address
explicitly.
This option results in less efficient code, but some strange hacks
Richard, if the documentation would have said explicitly that Werror
"makes warnings to prevent compilation", would you have understood it
better?
One proposal:
-Werror makes all warnings into errors, preventing compilation (see
also -Wfatal-errors).
On 12/05/06, Richard Guenther <[EMAIL PROT
On 5/12/06, D. Ensign <[EMAIL PROTECTED]> wrote:
> > I'd like to tell gcc to quit when a warning is encountered
> > (or even if a specific warning is encountered). Is there a way to do
> > this?
>
> Yes. -Werror. If you can tell us why you weren't able to find it in
> the documentation, perhaps
