public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dennis Clarke" <dclarke@blastwave.org>
To: "Hsieh, Pei-Ying (MED US)" <pei-ying.hsieh@siemens.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Compile gcc from source on a 64 bit OS ?
Date: Thu, 27 Dec 2007 21:24:00 -0000	[thread overview]
Message-ID: <2377.72.39.216.186.1198790653.squirrel@mail.blastwave.org> (raw)
In-Reply-To: <7AEC29D79CDD2646955922C34AFF1973124F3D@USMLVV1EXCTV06.ww005.siemens.n      et>


>
>
> Dear GCC developers/experts:
>
> I need to compile gcc from source on a 64 bit linux OS (Ubuntu and
> OpenSuSE).  After scanning through the installation procedures and
> manual, it is not clear to me how to do this on a 64 bit OS (default
> seems to be for 32 bit OS, using -m32).  It will be highly appreciated
> if you can shed some light on this.  Thanks!

http://gcc.gnu.org/gcc-4.2/changes.html

New Targets and Target Specific Improvements
IA-32/x86-64
-mtune=generic can now be used to generate code running well on common x86
chips. This includes AMD Athlon, AMD Opteron, Intel Pentium-M, Intel Pentium
4 and Intel Core 2.
-mtune=native and -march=native will produce code optimized for the host
architecture as detected using the cpuid instruction.
Added a new command-line option -fstackrealign and and __attribute__
((force_align_arg_pointer)) to realign the stack at runtime. This allows
functions compiled with a vector-aligned stack to be invoked from legacy
objects that keep only word-alignment.

I'm in the 64-bit Solaris world and a -m64 would work neatly.
Maybe even some -xarch or cpu specific target options.
Then again, you're in the linux land where anything can and will happen.
Are you thinking of working with GCC 4.2.2 or GCC 4.2.1 ? I have yet
to see GCC 4.2.2 build cleanly on a 64-bit OS but GCC 4.2.1 does.

see the bottom of http://gcc.gnu.org/gcc-4.2/buildstat.html where there are
a few x86_64-unknown-linux-gnu entries.

Merry Christmas.

Dennis

  parent reply	other threads:[~2007-12-27 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27 21:04 Hsieh, Pei-Ying (MED US)
     [not found] ` <7AEC29D79CDD2646955922C34AFF1973124F3D@USMLVV1EXCTV06.ww005.siemens.n      et>
2007-12-27 21:24   ` Dennis Clarke [this message]
2007-12-27 21:42 ` Andrew Haley
2007-12-27 22:00   ` Dennis Clarke
2007-12-28 10:25     ` Andrew Haley
2007-12-30 16:19       ` NightStrike
2007-12-30 20:28         ` Andrew Haley
2008-01-01 17:20         ` Tim Prince
2008-01-01 18:39           ` NightStrike
2008-01-02  0:14             ` Andrew Haley

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=2377.72.39.216.186.1198790653.squirrel@mail.blastwave.org \
    --to=dclarke@blastwave.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=pei-ying.hsieh@siemens.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).