From: ishikawa@yk.rim.or.jp
Cc: ebotcazou@gcc.gnu.org
Subject: (RFC) GCC minor document change: gcc.1
Date: Tue, 15 Jul 2003 08:52:40 +0900 (JST) [thread overview]
Message-ID: <m19cD7Y-000HHfC@standard.erephon> (raw)
I would like to propose a minor document change for gcc/doc/gcc.1
This is prompted by a change of GCC 3.3 (from 3.2.3)
that breaks GNU Emacs
installation, but the documentation is not clear enough IMHO.
Please see bugzilla 11386 entry for the background:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11386
The file is gcc/doc/gcc.1
If there are other popular programs that are affected,
I think their names should be explicitly mentioned.
(By doing so, we can save many debugging hours.)
I hope that similar clear warning is
incorporated into GNU Emacs's etc/MACHINES
document although future versions of GNU emacs
is probably free from the problem
thanks to Paul's patches.
However, there may be people who needed to
compile and install 21.3 and older versions
due to some reasons.
*** gcc.1.saved 2003-07-15 08:35:10.000000000 +0900
--- gcc.1 2003-07-15 08:36:10.000000000 +0900
***************
*** 3284,3290 ****
are initialized to zero into \s-1BSS\s0. This can save space in the resulting
code.
.Sp
! This option turns off this behavior because some programs explicitly
rely on variables going to the data section. E.g., so that the
resulting executable can find the beginning of that section and/or make
assumptions based on that.
--- 3284,3292 ----
are initialized to zero into \s-1BSS\s0. This can save space in the resulting
code.
.Sp
! This option turns off this behavior because some programs, most
! notably
! GNU Emacs 21.3 and its prior versions, explicitly
rely on variables going to the data section. E.g., so that the
resulting executable can find the beginning of that section and/or make
assumptions based on that.
Happy Hacking,
Ishikawa, Chiaki
PS: Sorry for some "message unavailable" missing
links in the related thread in emacs-devel.
I think this is due to my bounced messages.
I found out that my e-mail set up (for GNU emacs mail buffer) was
screwed up and that is why my previous attempt to post to
emacs-*@gnu.org bounced. GNU mailing list software is strict in that
From: address contains reachable address, I think.
I only realized the problem when I see my e-mail address was quoted as
ishikawa@bogus.example.com in a message posted by Paul (I cc:ed to
Paul.)
I am hoping this time, it works.
next reply other threads:[~2003-07-14 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 23:52 ishikawa [this message]
2003-07-14 23:55 ` (RFC) GCC minor document change: gcc.1 Andrew Pinski
2003-07-15 0:03 ` Ishikawa
2003-07-15 4:41 ` Jim Wilson
2003-07-15 5:46 ` Ishikawa
2003-07-15 7:34 ` Paul Eggert
2003-07-15 16:23 ` Ishikawa
2003-07-15 23:46 ` Ishikawa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m19cD7Y-000HHfC@standard.erephon \
--to=ishikawa@yk.rim.or.jp \
--cc=ebotcazou@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).