From: Jack Cummings <jack@ice.mudshark.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Alex Zhukov <szhukov@priocom.com>,
Janis Johnson <janis187@us.ibm.com>,
John Young <j.e.young@larc.nasa.gov>,
tom@tom.cc.wayne.edu, gcc@gcc.gnu.org
Subject: Re: 64 bit gcc?
Date: Thu, 01 Nov 2001 06:28:00 -0000 [thread overview]
Message-ID: <20011111212520.A22603@ice.mudshark.org> (raw)
In-Reply-To: <or4ro0yg9g.fsf@free.redhat.lsd.ic.unicamp.br>; from aoliva@redhat.com on Sun, Nov 11, 2001 at 10:39:07PM -0200
On Sun, Nov 11, 2001 at 10:39:07PM -0200, Alexandre Oliva wrote:
> The reason why GCC 3.0.x and earlier are regarded as not fully
> supporting 64-bit sparc are two:
> - sometimes, variables of type double are misaligned in the stack,
> such that if a load or store instruction that requires alignment to
> 8 bytes boundaries is used, your program will crash with a SIGBUS
> - infrastructure needed to fully represent the 64-bit sparc ABI was
> missing in GCC 3.0.x, even though it was already present as a patch
> in Red Hat's GCC 2.96. It was deemed to risky for GCC 3.0, and was
> only merged into the GCC CVS tree after the 3.0 branch was created.
Thanks for the explanation.
I will look into 3.1.
--Jack
next prev parent reply other threads:[~2001-11-12 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 9:00 John Young
2001-10-18 12:49 ` Janis Johnson
2001-10-19 4:33 ` Gerald Pfeifer
2001-10-21 16:37 ` Alex Zhukov
2001-10-21 16:44 ` Jack Cummings
2001-10-22 1:20 ` Alex Zhukov
2001-11-01 5:44 ` Alexandre Oliva
2001-11-01 6:28 ` Jack Cummings [this message]
2001-10-18 13:33 John Young
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011111212520.A22603@ice.mudshark.org \
--to=jack@ice.mudshark.org \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=j.e.young@larc.nasa.gov \
--cc=janis187@us.ibm.com \
--cc=szhukov@priocom.com \
--cc=tom@tom.cc.wayne.edu \
/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).