[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."
From: |
Richard Kenner |
Subject: |
Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..." |
Date: |
Mon, 01 Jan 2007 22:27:24 EST |
> I don't think -frisky is a good name for that option. A better name
> would be -fstrict.
Or -pedantic? ;-)
> 4) We permit an exception to occur if there is a signed overflow. If
> we can prove that some expression causes signed overflow, we are
> permitted to assume that that case will never arise.
>
> Case 4 actually never arises at present, and I can't imagine any
> reason that it would be desirable.
Agreed. Going down this direction leads to Robert's "erase the disk"
example.
- Re: changing "configure" to default to "gcc -g -O2 -fwrapv ...", (continued)
- Re: changing "configure" to default to "gcc -g -O2 -fwrapv ...", Paul Eggert, 2007/01/02
- Autoconf manual's coverage of signed integer overflow & portability, Paul Eggert, 2007/01/02
- Re: Autoconf manual's coverage of signed integer overflow & portability, Richard Kenner, 2007/01/02
- Re: Autoconf manual's coverage of signed integer overflow & portability, Paul Eggert, 2007/01/02
- Re: Autoconf manual's coverage of signed integer overflow & portability, Richard Kenner, 2007/01/02
- Re: Autoconf manual's coverage of signed integer overflow & portability, Paul Eggert, 2007/01/03
- Re: Autoconf manual's coverage of signed integer overflow & portability, Andrew Pinski, 2007/01/03
- Re: Autoconf manual's coverage of signed integer overflow & portability, Gabriel Dos Reis, 2007/01/03
- Re: Autoconf manual's coverage of signed integer overflow & portability, Paul Eggert, 2007/01/03