From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features
Date: Mon, 25 Jul 2011 13:43:19 -0700 [thread overview]
Message-ID: <4E2DD567.5060303@mentor.com> (raw)
In-Reply-To: <1311626348.3098.20.camel@lenovo.internal.reciva.com>
On 07/25/2011 01:39 PM, Phil Blundell wrote:
> On Mon, 2011-07-25 at 12:34 -0700, Tom Rini wrote:
>> On 07/25/2011 11:55 AM, Mark Hatle wrote:
>>> I actually prefer "x86-64" I think that is a reasonable compromise between the
>>> x86_64 naming and the need to not use "_".
>>
>> That causes other problems, no? Top of my head would be that deb/ipk
>> doesn't allow a dash in that field. Could be mistaken tho...
>
> The package management backend could always rewrite it to something else
> (under control of the DISTRO if need be, so AMD and Intel folks can each
> call it their own thing if they want to).
>
> Personally though, I would be tempted just to call it "x64", which is
> then nicely symmetric with x32 and doesn't seem likely to collide with
> anything else.
Yeah, but x32 means something else (not i586, etc) :) My main
suggestion is to follow existing conventions, so amd64 since we can't
match x86_64 like the RPM world. FWIW, x64 appears to be the MS ABI for
this case, so.. not a bad idea?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-07-25 20:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 14:49 [PATCH 0/3] First round of tune config file updates Richard Purdie
2011-07-22 14:49 ` [PATCH 1/3] bitbake.conf/cross.bbclass: Add ability to dynamically change library location Richard Purdie
2011-07-22 14:49 ` [PATCH 2/3] conf/machine/tune: Overhaul tune include file variables Richard Purdie
2011-07-22 15:03 ` Kumar Gala
2011-07-22 15:13 ` Richard Purdie
2011-07-22 14:49 ` [PATCH 3/3] conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCH Richard Purdie
2011-07-22 14:54 ` Koen Kooi
2011-07-22 15:11 ` Richard Purdie
2011-07-22 15:15 ` Koen Kooi
2011-07-22 18:00 ` [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features Richard Purdie
2011-07-22 18:14 ` Tom Rini
2011-07-25 18:55 ` Mark Hatle
2011-07-25 19:34 ` Tom Rini
2011-07-25 19:39 ` Mark Hatle
2011-07-25 20:39 ` Phil Blundell
2011-07-25 20:43 ` Tom Rini [this message]
2011-07-22 18:00 ` [PATCH 4/3] bitbake.conf/classes: Variable cleanup Richard Purdie
2011-07-22 18:01 ` [PATCH 6/3] Move architecture specific TARGET_OS mangling into tune files Richard Purdie
2011-07-25 13:42 ` Richard Purdie
2011-07-25 16:23 ` Phil Blundell
2011-07-27 16:37 ` Richard Purdie
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=4E2DD567.5060303@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@lists.openembedded.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