From: Bruce Korb <bkorb@veritas.com>
Cc: guile-devel@gnu.org
Subject: Re: gcc's catching more "errors" now...
Date: Fri, 09 May 2003 09:20:16 -0700 [thread overview]
Message-ID: <3EBBD540.3336100F@veritas.com> (raw)
In-Reply-To: 87he8414y5.fsf@raven.i.defaultvalue.org
Rob Browning wrote:
>
> I tried configuring with CC=gcc-3.3, and we get:
>
> gcc-3.3 -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -I../libguile-ltdl -g -O2 -Werror -Wall -Wmissing-prototypes -MT eval.lo -MD -MP -MF .deps/eval.Tpo -c eval.c -fPIC -DPIC -o .libs/eval.lo
> eval.c: In function `scm_ceval':
> eval.c:1966: warning: dereferencing type-punned pointer will break strict-aliasing rules
> In file included from eval.c:4591:
> eval.c: In function `scm_deval':
> eval.c:1966: warning: dereferencing type-punned pointer will break strict-aliasing rules
>
> which is complaining about this:
>
> if (scm_stack_checking_enabled_p
> && SCM_STACK_OVERFLOW_P ((SCM_STACKITEM *) &proc))
> {
void* p_proc = &proc;
> if (scm_stack_checking_enabled_p
> && SCM_STACK_OVERFLOW_P ((SCM_STACKITEM *) p_proc))
"void*" may alias anything.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-05-09 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 16:05 gcc's catching more "errors" now Rob Browning
2003-05-09 16:20 ` Bruce Korb [this message]
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=3EBBD540.3336100F@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).