From: "Måns Rullgård" <mans@mansr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Specific support for Intel Atom architecture
Date: Sun, 03 May 2009 20:38:20 +0100 [thread overview]
Message-ID: <yw1x4ow2ugcz.fsf@ps3.mansr.com> (raw)
In-Reply-To: 49FDE47C.7090607@zytor.com
"H. Peter Anvin" <hpa@zytor.com> writes:
> Willy Tarreau wrote:
>>>>>
>>>>> $(call cc-option,-march=atom,-march=i686)
>>>> if it's an in-order architecture, wouldn't it be better to tune for
>>>> i386 or i486 instead ?
>>> -march isn't about tuning, it's about supported instructions.
>>
>> agreed, but unless specified otherwise using -mtune, -march also sets
>> default tuning for the indicated CPU. At least in my experience.
>>
>>> The right line is
>>> $(call cc-option,-march=atom,-march=core2)
>
> For really old gcc's (we support all the way back to gcc 3.2 still)
> -march=core2 might not work either.
-march=core2 support was added in gcc 4.3.
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2009-05-03 19:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 12:08 Specific support for Intel Atom architecture Tobias Doerffel
2009-04-30 15:40 ` Ingo Molnar
2009-04-30 17:03 ` H. Peter Anvin
2009-04-30 17:10 ` H. Peter Anvin
2009-05-03 5:38 ` Willy Tarreau
2009-05-03 6:48 ` H. Peter Anvin
2009-05-03 11:08 ` Tobias Doerffel
2009-05-04 13:14 ` Ingo Molnar
2009-05-04 13:32 ` Arjan van de Ven
2009-05-04 17:55 ` Ingo Molnar
2009-05-03 14:53 ` Arjan van de Ven
2009-05-03 18:30 ` Willy Tarreau
2009-05-03 18:37 ` H. Peter Anvin
2009-05-03 19:38 ` Måns Rullgård [this message]
2009-05-04 7:22 ` Andi Kleen
2009-05-11 21:30 ` Tobias Doerffel
2009-05-12 6:53 ` Andi Kleen
2009-05-12 14:20 ` Ulrich Drepper
2009-05-12 15:04 ` Andi Kleen
2009-05-12 17:45 ` Ulrich Drepper
2009-05-12 18:13 ` Andi Kleen
2009-05-14 5:04 ` Harvey Harrison
2009-05-14 13:38 ` Ulrich Drepper
2009-05-14 14:01 ` Andi Kleen
2009-05-14 16:19 ` Ulrich Drepper
2009-05-14 17:29 ` Andi Kleen
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=yw1x4ow2ugcz.fsf@ps3.mansr.com \
--to=mans@mansr.com \
--cc=linux-kernel@vger.kernel.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