From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Everyone working on the C side might want to read this article...
Date: Mon, 28 Apr 2003 17:30:41 -0500 [thread overview]
Message-ID: <87znmajlv2.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <3EAD96EC.57F41CA7@veritas.com> (Bruce Korb's message of "Mon, 28 Apr 2003 14:02:36 -0700")
Bruce Korb <bkorb@veritas.com> writes:
> The default optimization is sufficient for many of the aliasing
> problems. If you compile with the GCC 3.3 branch -Wall will trigger
> some extra aliasing-related warnings. Examine the warnings carefully.
> Remember that just because it didn't warn doesn't mean there isn't
> a problem. However, the warnings do actually cover most of the common
> ways aliasing breaks code.
Anyone running Debian who's interested in working on this, try
# apt-get install gcc-3.3
$ cd src/guile/head/
$ CC=gcc-3.3 ./configure ...
$ make clean
$ make
This shouldn't affect your existing gcc 3.2 install, i.e. gcc
--version should still give you 3.2...
We use -Wall -Werror by default now (in the unstable branch), so
you'll get those options automatically. From an initial test, it
looks like we've at least got a new slew of signed/unsigned compare
warnings.
--
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
prev parent reply other threads:[~2003-04-28 22:30 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
2003-04-28 21:02 ` Bruce Korb
2003-04-28 22:30 ` Rob Browning [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=87znmajlv2.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).