From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: yjkim@SPring8.or.jp
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: How to use SPARC m64 option of gcc-3.0.2
Date: Thu, 06 Dec 2001 06:58:00 -0000 [thread overview]
Message-ID: <yddsnaowg5b.fsf@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: "Yujong Kim"'s message of "Thu, 6 Dec 2001 23:33:16 +0900"
"Yujong Kim" <yjkim@postech.ac.kr> writes:
> Please, would tell me the way how I can use -m64 option to compile my code with 64-bit ?
> May I reinstall the gcc-3.0.2 with other configure option to use -m64 option in my machine ?
GCC 3.0.x doesn't support 64-bit code on Solaris 7/8. The installation
manual states:
Starting with Solaris 7, the operating system is capable of executing
64-bit SPARC V9 binaries. GCC 3.0 doesn't properly support this yet.
Although some patches or recipes to enable this support have been posted
to various newsgroups and mailing lists, we recommend against using
them, since the compiler may either crash or, worse, silently generate
bad code. If you really need this capability now, you might try a CVS
version of GCC 3.1, which will fully support this. If all you want is
code tuned for the UltraSPARC CPU, you should try the
@option{-mtune=ultrasparc} option instead, which should be safe from
those bugs and produce code that, unlike full 64-bit code, can still run
on non-UltraSPARC machines.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE
prev parent reply other threads:[~2001-12-06 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 6:29 Yujong Kim
2001-12-06 6:58 ` Rainer Orth [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yddsnaowg5b.fsf@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=yjkim@SPring8.or.jp \
/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).