public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dennis Wassel" <dennis.wassel@googlemail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: how to enable -m64 on x86-linux for building ATLAS
Date: Sat, 05 Apr 2008 13:01:00 -0000	[thread overview]
Message-ID: <fe03ae8f0804050210y55ef9c5fvdfc9472a72086a46@mail.gmail.com> (raw)
In-Reply-To: <47F6E59C.8E1FE3AF@dessent.net>

2008/4/5, Brian Dessent <brian@dessent.net>:
> Dennis Wassel wrote:
>
>  > I've been trying to compile the ATLAS library on an 32-bit Linux
>  > system with my self-compiled gcc 4.3.0, but this fails.
>  > It boils down to the ATLAS config utility noticing that I have a
>  > 64-bit processor and trying to compile some low-level stuff with -m64,
>  > which doesn't work because I have not compiled in 64-bit support. [I
>  > could force 32-bit mode, but I feel that 64-bit mode surely improves
>  > performance, which is what ATLAS is for in the first place]
>
>
> You could build a cross compiler, but what would be the point?  You're
>  running a 32 bit operating system which means you can't run 64 bit
>  binaries, even if you have a processor capable of doing so.  The
>  resulting output would be totally useless.  As Andrew said it only works
>  in the other direction.
>
>  It is also possible to build a native gcc that supports -m64 on a 32 bit
>  host.  To do so requires first installing the 64 bit libc headers and
>  libraries in the appropriate places (normally done through your distro's
>  package manager) as well as an x86_64 binutils in the same prefix and
>  then using --enable-targets=all when configuring.  If you're not root
>  this will likely be impossible since you can't write to /usr/lib64 or
>  whatever, so you'll have to go with the cross-compiler method.  But
>  again, simply switching to a 64 bit operating system is what is actually
>  required here since then gcc will generate 64 bit binaries by default,
>  and you'll actually be able to run the resulting binary.
>
>
>  Brian
>

I've had a feeling that a cross-compiler is what I need -- you confirm
that, thanks a lot!
What strikes me about this is the fact that ATLAS' configure (all by
itself, no options given) thinks that using -m64 on a 32-bit system
might be a good idea (not to actually link something executable,
probably just some low-level assembler-ish stuff, no clue), since I'm
using a 64-bit compiler - am I up to something here, or do you think
it's just One Of Those Things?

Dennis

  reply	other threads:[~2008-04-05  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  9:02 Dennis Wassel
2008-04-03 10:27 ` Andrew Haley
2008-04-03 17:22 ` Matthew Woehlke
2008-04-05  5:40 ` Brian Dessent
2008-04-05 13:01   ` Dennis Wassel [this message]
2008-04-05 23:53     ` Brian Dessent
2008-04-06  6:37       ` Brian Dessent

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=fe03ae8f0804050210y55ef9c5fvdfc9472a72086a46@mail.gmail.com \
    --to=dennis.wassel@googlemail.com \
    --cc=gcc-help@gcc.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).