From: Bruce Korb <bkorb@veritas.com>
Cc: guile-devel@gnu.org
Subject: Re: Compiling 1.7.0 with gcc-3.3
Date: Mon, 19 May 2003 10:05:41 -0700 [thread overview]
Message-ID: <3EC90EE5.832CB36E@veritas.com> (raw)
In-Reply-To: 87el2vovvt.fsf@raven.i.defaultvalue.org
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
next prev parent reply other threads:[~2003-05-19 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 10:09 Compiling 1.7.0 with gcc-3.3 Mikael Djurfeldt
2003-05-19 14:26 ` Rob Browning
2003-05-19 17:05 ` Bruce Korb [this message]
2003-05-22 10:26 ` Mikael Djurfeldt
2003-05-19 16:20 ` Bruce Korb
2003-05-22 9:37 ` Mikael Djurfeldt
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EC90EE5.832CB36E@veritas.com \
--to=bkorb@veritas.com \
--cc=guile-devel@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).