From: Andrew Haley <aph@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Me Myself and I <stargate7thsymbol@live.co.uk>,
gcc-help@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: No gcj 64 bit compilation support? What the?
Date: Thu, 15 Sep 2011 09:07:00 -0000 [thread overview]
Message-ID: <4E71C050.5040907@redhat.com> (raw)
In-Reply-To: <CAH6eHdQKAGf3R-3zM2otm6LkcpoWhFO__ZebMB==gr_bH1b1QQ@mail.gmail.com>
On 09/15/2011 09:43 AM, Jonathan Wakely wrote:
> On 15 September 2011 09:39, Andrew Haley wrote:
>> On 09/15/2011 09:16 AM, Me Myself and I wrote:
>>
>>>
>>> Then why is this, if my compiler is on a 64 bit operating system with
>>> 64 bit hardware? Shouldn't it compile to 64 bit files anyway?
>>> Isn't the operating system really doing this by default? Is this my reply really accurate?
>>> If not, why not? Where can I find simple instructions to build gcj
>>> to compile 64 bit optimised executable files?
>>
>> We don't know the answers to any of these questions because we don't
>> know who built the gcj you're using or what OS it runs on.
>
> The OP mentioned Mandriva 2011 but that still doesn't tell us much,
> this is a gcc list not a Mandriva one so we don't know about the
> distro or what packages are installed.
Ah yes, sorry. I don't know anything about Mandriva.
I really don't know why anyone would want to use -m64 on a 64-bit host.
64-bit is going to be the default anyway. I have no idea why you'd get
an error from -m64, though.
Someone who knows Mandriva may know the answers to these questions.
Andrew.
prev parent reply other threads:[~2011-09-15 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 8:16 Me Myself and I
2011-09-15 8:33 ` Chris Burdess
2011-09-15 8:39 ` Andrew Haley
2011-09-15 8:44 ` Jonathan Wakely
2011-09-15 9:07 ` Andrew Haley [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=4E71C050.5040907@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=stargate7thsymbol@live.co.uk \
/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).