From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Re: display word wrapping Date: Mon, 31 May 2004 19:55:53 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <2914-Mon31May2004195553+0300-eliz@gnu.org> References: <20040531013831.AA50.LEKTU@mi.madritel.es> <20040531153907.3F41.JMBARRANQUERO@wke.es> Reply-To: Eli Zaretskii NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1086022737 17287 80.91.224.253 (31 May 2004 16:58:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 31 May 2004 16:58:57 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon May 31 18:58:51 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BUq7f-0004jC-00 for ; Mon, 31 May 2004 18:58:51 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BUq7f-0005e1-00 for ; Mon, 31 May 2004 18:58:51 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BUq7q-0003Xm-M4 for emacs-devel@quimby.gnus.org; Mon, 31 May 2004 12:59:02 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BUq7j-0003XU-61 for emacs-devel@gnu.org; Mon, 31 May 2004 12:58:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BUq7f-0003X2-0g for emacs-devel@gnu.org; Mon, 31 May 2004 12:58:53 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BUq7e-0003Wy-NN for emacs-devel@gnu.org; Mon, 31 May 2004 12:58:50 -0400 Original-Received: from [192.114.186.23] (helo=aragorn.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BUq7D-00072Z-U1 for emacs-devel@gnu.org; Mon, 31 May 2004 12:58:24 -0400 Original-Received: from zaretski ([80.230.152.211]) by aragorn.inter.net.il (MOS 3.4.6-GR) with ESMTP id CZO41963; Mon, 31 May 2004 19:58:01 +0300 (IDT) Original-To: Juanma Barranquero X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <20040531153907.3F41.JMBARRANQUERO@wke.es> (message from Juanma Barranquero on Mon, 31 May 2004 16:40:41 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:24286 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24286 > Date: Mon, 31 May 2004 16:40:41 +0200 > From: Juanma Barranquero > > I suppose the optimizer's assuming the variable doesn't need to be > really volatile, because it is a stack var whose address is not > taken. It isn't allowed to assume that. AFAIK, unlike the `register' qualifier, `volatile' is not an advisory one, it's mandatory. But as Andreas points out, the declaration itself is incorrect. If so, changing it to whatever is right should make a difference. Here, try this: struct image * volatile img; Did that work? > > But such a workaround needs > > to be more clever than the push/pop pair above, since it needs to > > update img->load_failed_p AFTER restoring img, not before it. > > Yes, I know. I was just testing different local/static situations. So perhaps we should just do it now.