This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc options to use

From: me22 <me22 dot ca at gmail dot com>
To: "Koornstra, Reinoud" <koornstra at hp dot com>
Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: Thu, 19 Mar 2009 15:55:28 -0400
Subject: Re: gcc options to use
References: <E92FAF79A8BBC642A36EEE3AA7F152D8341C6F5595@GVW1089EXB.americas.hpqcorp.net> <m3tz669jvp.fsf@google.com> <E92FAF79A8BBC642A36EEE3AA7F152D83CF384C322@GVW1089EXB.americas.hpqcorp.net> <m3sklm3p5x.fsf@google.com> <E92FAF79A8BBC642A36EEE3AA7F152D83CF384C95B@GVW1089EXB.americas.hpqcorp.net> <49B78C61.9070705@wippies.com> <E92FAF79A8BBC642A36EEE3AA7F152D83CF3B84ECD@GVW1089EXB.americas.hpqcorp.net>

On Thu, Mar 19, 2009 at 15:37, Koornstra, Reinoud <koornstra@hp.com> wrote:
>
> I am compiling some libs and binaries for core2 duo cpu machines.
> The gcc version is 4.3.3 and the arguments I use are:
>
> x86_64-unknown-linux-gnu-gcc -m64 -march=core2 -mtune=core2 bla bla.
> When I read the compiled bin with readelf it reports this:
>
> Class: ELF64
> Machine: Advanced Micro Devices X86-64
> Etc etc.
>
> I guess this is alright....?
>

Well readelf would have no idea for which processor the program was
tuned, so it presumably can only report the instruction set, which was
developed by AMD.

Seems alright to me,
~ Scott

References:
- libstdc issue
  - From: Koornstra, Reinoud
- Re: libstdc issue
  - From: Ian Lance Taylor
- which glibc to use
  - From: Koornstra, Reinoud
- Re: which glibc to use
  - From: Ian Lance Taylor
- RE: which glibc to use
  - From: Koornstra, Reinoud
- Re: which glibc to use
  - From: Kai Ruottu
- gcc options to use
  - From: Koornstra, Reinoud

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]