public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense
Date: Mon, 16 Jul 2001 17:06:00 -0000 [thread overview]
Message-ID: <20010717000600.2772.qmail@sourceware.cygnus.com> (raw)
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
next reply other threads:[~2001-07-16 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 17:06 Enrico Scholz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 20:36 Gabriel Dos Reis
2001-07-13 17:36 Enrico Scholz
2001-07-13 13:56 Enrico Scholz
2001-07-13 13:46 Enrico Scholz
2001-07-13 13:36 Phil Edwards
2001-07-13 13:26 Enrico Scholz
2001-07-12 12:56 Phil Edwards
2001-07-12 5:06 Gabriel Dos Reis
2001-07-12 4:06 Enrico Scholz
2001-07-12 1:46 Gabriel Dos Reis
2001-07-11 14:56 enrico.scholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010717000600.2772.qmail@sourceware.cygnus.com \
--to=enrico.scholz@informatik.tu-chemnitz.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).