This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense
- To: nobody at gcc dot gnu dot org
- Subject: Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense
- From: Enrico Scholz <enrico dot scholz at informatik dot tu-chemnitz dot de>
- Date: 17 Jul 2001 00:06:00 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Enrico Scholz <enrico dot scholz at informatik dot tu-chemnitz dot de>
The following reply was made to PR bootstrap/3653; it has been noted by GNATS.
From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
To: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense
Date: 17 Jul 2001 02:01:07 +0200
Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr> writes:
> [...options not understood by former gcc versions and -fmessage-length...]
> | Either these options have not changed behavior or there was a technical
> | reason to change it.
>
> There was a technical reason for -fmessage-length.
Please tell me the technical reason which caused the swap of the default
behavior from non-wrapping to wrap-and-break-tools mode!
Made other options line-wrapping by default necessarily, is the generated
code faster or opens -fmessage-length=72 doors to better optimizations?
Don't take it amiss but I can not understand why line-wrapping is enabled
by default.
Enrico