From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Ishikawa Newsgroups: gmane.comp.gcc.patches,gmane.emacs.devel Subject: Re: (RFC) GCC minor document change: gcc.1 Date: Wed, 16 Jul 2003 01:23:30 +0900 Sender: gcc-patches-owner@gcc.gnu.org Message-ID: <3F142A82.9B5E17AD@yk.rim.or.jp> References: <9EF8DA0A-B656-11D7-8A0C-000393A6D2F2@physics.uc.edu> <3F1344D4.9BCA454@yk.rim.or.jp> <200307150734.h6F7YLi13759@green.twinsun.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1058286084 16185 80.91.224.249 (15 Jul 2003 16:21:24 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 15 Jul 2003 16:21:24 +0000 (UTC) Cc: gcc-patches@gcc.gnu.org, emacs-pretesters@gnu.org, emacs-devel@gnu.org, ebotcazou@gcc.gnu.org Original-X-From: gcc-patches-return-92340-gcc-patches=m.gmane.org@gcc.gnu.org Tue Jul 15 18:21:23 2003 Return-path: Original-Received: from sources.redhat.com ([67.72.78.213]) by main.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 19cSXk-00048m-00 for ; Tue, 15 Jul 2003 18:20:44 +0200 Original-Received: (qmail 28893 invoked by alias); 15 Jul 2003 16:21:40 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Archive: List-Post: List-Help: Original-Received: (qmail 28877 invoked from network); 15 Jul 2003 16:21:38 -0000 Original-Received: from unknown (HELO standard.erephon) (210.139.43.211) by sources.redhat.com with SMTP; 15 Jul 2003 16:21:38 -0000 Original-Received: from yk.rim.or.jp (really [127.0.0.1]) by yk.rim.or.jp via smail with esmtp id (Debian Smail3.2.0.114) for ; Wed, 16 Jul 2003 01:23:32 +0900 (JST) X-Accept-Language: ja, en Original-To: Paul Eggert Xref: main.gmane.org gmane.comp.gcc.patches:37288 gmane.emacs.devel:15624 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:15624 Paul Eggert wrote: > > > Date: Tue, 15 Jul 2003 09:03:32 +0900 > > From: Ishikawa > > > ! This option turns off this behavior because some programs, > > ! most notably GNU Emacs 21.3 and prior versions, > > ! explicitly > > rely on variables going to the data section. > > This statement is misleading, for two reasons. First, this is merely > an efficiency issue for Emacs; it is not a correct-behavior issue. > Second, I don't know of any real hosts where the efficiency issue > actually arises. > > I am mainly responsible for this misunderstanding, since I originally > sent incorrect messages to emacs-devel and emacs-pretesters implying > that -fno-zero-initialized-in-bss caused the core dump on Solaris 8. > (I was wrong: the real bug was in Emacs's src/unexelf.c.) > So I'd like to make amends by clarifying the two issues as best I can. > [ ... ] Dear Paul, Thank you for your clarification. So it means that, basically, the new code layout somehow produced by GCC 3.3 triggered a bug in unexelf.c, which was fixed in your previous posting. OK, then we don't have to put the change in the gcc documentation about -fno-zero-initialized-in-bss causing problems for GNU Emacs (although I certainly can believe some embedded folks will be bitten for once when I think about it, but I digress.). Below is not directed to Paul per se, but to the CC:s mailing lists. Now I am wondering what we should do about the problem of GCC 3.3 + and unpatched GNU Emacs 21.3 combination under Solaris 8. Since GCC 3.2.3 + GNU Emacs 21.3 works and GCC 3.3 + GNU Emacs 21.3 doesn't, I still would like to see a mention of the problem in some visible places unless GNU Emacs 21.4 that fixes this problem is released very soon. But where should we put the warning? My feeling as the end user is on gcc's changes.html, but there may be a better place. It is a pity that GCC 3.3's change page doen't mention this zero-initialized-in-bss feature of GCC 3.3 in any case. At the end of GCC 3.3's changes.html, it says: >Please send comments on these web pages and GCC to our public mailing list at gcc@gnu.org or gcc@gcc.gnu.org, send >other questions to gnu@gnu.org. Is sending this to gcc-patches enough or should I send to gcc mailing list as well? Happy Hacking, Ishikawa, Chiaki PS: For reasons I don't know (maybe my netscape's MIME header specifying ISO-2022-JP is not liked by the mailing list software), my post to emacs-pretester seems to bounce constantly. Again sorry if there is a hole in the threaded listing of the mailing archive. -- int main(void){int j=2003;/*(c)2003 cishikawa. */ char t[] =" @abcdefghijklmnopqrstuvwxyz.,\n\""; char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz"; while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1), (putchar(t[j])));return 0;}/* under GPL */