From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Everyone working on the C side might want to read this article...
Date: Mon, 28 Apr 2003 15:48:26 -0500 [thread overview]
Message-ID: <87llxul55x.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <873ckgevxl.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 17 Apr 2003 15:00:22 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
> The following article explains gcc changes that may be behind at least
> some of our recent set of bugs:
>
> http://www.ddj.com/documents/s=880/ddj0010d/0010d.htm
So does anyone have thoughts about how we should approach this issue?
How common do we think these type aliasing problems might be in our
code, and if we do have problems, can we just fix each offending bit
of code with temp assignments or other "disambiguating" statements, or
is there some higher level way we might be able to address the issue
(i.e. could a union help here, something else?).
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-04-28 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 20:00 Everyone working on the C side might want to read this article Rob Browning
2003-04-17 20:25 ` Bruce Korb
2003-04-17 20:33 ` Dale P. Smith
2003-04-28 20:48 ` Rob Browning [this message]
2003-04-28 21:02 ` Bruce Korb
2003-04-28 22:30 ` Rob Browning
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=87llxul55x.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).