From: Andy Wingo <wingo@pobox.com>
Subject: Re: 1.8 status and 64-bit data corruption
Date: Wed, 29 Mar 2006 12:07:42 +0200 [thread overview]
Message-ID: <1143626862.5187.115.camel@localhost.localdomain> (raw)
In-Reply-To: <87fyl2i8yw.fsf@ossau.uklinux.net>
Hi Neil,
On Tue, 2006-03-28 at 21:56 +0100, Neil Jerram wrote:
> The gcc on this machine is:
>
> neil@we:~/guile-core-1.8-20060328$ gcc --version
> gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
I got different results when using gcc 3.3. Can't remember exactly how
different tho :-/
The gcc I normally use is 4.0.3. I just reproduced the bug with that gcc
and latest guile, running with the default cflags (-g -O2). The error is
highly dependent on cflags tho.
Regards,
--
Andy Wingo
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-03-29 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 13:08 1.8 status and 64-bit data corruption Neil Jerram
2006-03-28 20:56 ` Neil Jerram
2006-03-29 10:07 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-29 15:12 Bill Schottstaedt
2006-03-29 15:40 ` Jay Cotton
2006-04-15 12:45 Bill Schottstaedt
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=1143626862.5187.115.camel@localhost.localdomain \
--to=wingo@pobox.com \
/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).