Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] GCC - march=geode doesn't exist?
Date: Fri, 27 Jul 2007 18:24:04 +0200	[thread overview]
Message-ID: <20070727162404.GG25147@aon.at> (raw)
In-Reply-To: <20070723175420.GE9995@aon.at>

William,

On Mon, Jul 23, 2007 at 07:54:20PM +0200, Bernhard Fischer wrote:
>On Thu, Jul 19, 2007 at 02:35:15PM +1000, William Pettersson wrote:
>>Ok, so I'm still working on this Soekris, using gcc-4.2.0.  4.2.0
>>doesn't support -march=geode or -mtune=geode, but BR2_GCC_TARGET_ARCH
>>and BR2_GCC_TARGET_TUNE are both set to "geode" if you select the geode.
>> Now apparently gcc-4.3.0 has plans for a geode target, but as 4.3.0
>>isn't stable yet, I've attached a patch which makes the "geode" select
>>"i586" for BR2_GCC_TARGET_TUNE and BR2_GCC_TARGET_ARCH.
>
>Yes, somebody already mentioned about the same for itanium. I added
>those bits with just a copy of gcc-trunk at hand..
>
>Can you check your manpage of gcc-4.2 to see what itanium variants are
>supported there and fix those and geode according to:
>
>default foo if BR2_foo && BR2_GCC_VERSION_4_3
>default bar if BR2_foo && !BR2_GCC_VERSION_4_3
>
>default baz1 if BR2_baz && (BR2_GCC_VERSION_3_4 || 4_0 || 4_1)
>etc..
>
>TIA,

ping
Would be awesome if you could have a look into this..

      reply	other threads:[~2007-07-27 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19  4:35 [Buildroot] GCC - march=geode doesn't exist? William Pettersson
2007-07-23 17:54 ` Bernhard Fischer
2007-07-27 16:24   ` Bernhard Fischer [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=20070727162404.GG25147@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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