From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Bruce Korb Newsgroups: gmane.lisp.guile.bugs,gmane.lisp.guile.devel Subject: Re: Compiling 1.7.0 with gcc-3.3 Date: Mon, 19 May 2003 10:05:41 -0700 Organization: Home Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Message-ID: <3EC90EE5.832CB36E@veritas.com> References: <87el2vovvt.fsf@raven.i.defaultvalue.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1053369538 32712 80.91.224.249 (19 May 2003 18:38:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 19 May 2003 18:38:58 +0000 (UTC) Cc: guile-devel@gnu.org Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Mon May 19 20:38:54 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19HpVN-0008M2-00 for ; Mon, 19 May 2003 20:37:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19HpTa-0003Yh-07 for guile-bugs@m.gmane.org; Mon, 19 May 2003 14:35:10 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19HpTK-0003Xz-00 for bug-guile@gnu.org; Mon, 19 May 2003 14:34:54 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19HoEp-0005Hz-00 for bug-guile@gnu.org; Mon, 19 May 2003 13:15:54 -0400 Original-Received: from bay-bridge.veritas.com ([143.127.3.10] helo=mtvmime02.veritas.com) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19Hnwl-0002bY-00; Mon, 19 May 2003 12:57:11 -0400 Original-Received: from megami (unverified) by mtvmime02.veritas.com (Content Technologies SMTPRS 4.3.6) with SMTP id ; Mon, 19 May 2003 09:59:01 -0700 Original-Received: from veritas.com ([172.22.12.211]) (1808 bytes) by megami via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Mon, 19 May 2003 09:57:09 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #15 built 2001-Aug-30) X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.19-4GB i686) X-Accept-Language: en Original-To: Rob Browning Original-cc: Mikael Djurfeldt Original-cc: bug-guile@gnu.org X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GUILE, GNU's Ubiquitous Extension Language List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.bugs:800 gmane.lisp.guile.devel:2414 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.bugs:800 Rob Browning wrote: > > eval.c:1965: > > if (scm_stack_checking_enabled_p > > && SCM_STACK_OVERFLOW_P ((SCM_STACKITEM *) &proc)) > > Right I posted this to guile-devel a week or so ago. Someone posted a > (void *) coercion fix, but I haven't had a chance to look in to it. > > > This could be "solved" by adding -Wno-strict-aliasing to the > > compilation options, but that might remove better motivated warnings. > > I'd be happier with -fno-strict-aliasing, but I don't really want that > either. I'd rather see if we can alter the code to avoid the warning. The (void*) coercion explicitly tells the compiler that the memory named ``proc'' can be referenced in aliasing-unfriendly ways. The other mechanism is to make ``proc'' be a union of whatever it currently is with SCM_STACKITEM, so that other references become: proc.normal and this reference becomes (without a cast): &proc.stackitem In this context, ``(uintptr_t)&proc'' seems more appropriate and less hassle, but it's your call. _______________________________________________ Bug-guile mailing list Bug-guile@gnu.org http://mail.gnu.org/mailman/listinfo/bug-guile