From: Andrew Stubbs <ams@codesourcery.com>
Cc: Richard Earnshaw <rearnsha@arm.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"patches@linaro.org" <patches@linaro.org>
Subject: Re: [PATCH][ARM] -m{cpu,tune,arch}=native
Date: Thu, 13 Oct 2011 15:08:00 -0000 [thread overview]
Message-ID: <4E96F5D9.6090207@codesourcery.com> (raw)
In-Reply-To: <4E787025.1040402@codesourcery.com>
Ping.
On 20/09/11 11:51, Andrew Stubbs wrote:
> On 09/09/11 12:55, Richard Earnshaw wrote:
>> The part number field is meaningless outside of the context of a a
>> specific vendor -- only taken as a pair can they refer to a specific
>> part. So why is the vendor field hard-coded rather than factored into
>> the table of parts.
>>
>> Maybe it would be better to have a table of tables, with the top-level
>> table being indexed by vendor id. Something like
>
> Yes, but since I only have part numbers for one vendor, I left that sort
> of thing out on the principle that it's best not to add complexity until
> you need it.
>
> Anyway, I have done it now, so here it is. :)
>
> I've also fixed the problem that if it didn't recognise the CPU, it
> defaulted to the hard default, ignoring the --with-cpu configured default.
>
> OK?
>
> Andrew
next prev parent reply other threads:[~2011-10-13 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 16:16 Andrew Stubbs
2011-08-26 17:17 ` Joseph S. Myers
2011-08-28 9:43 ` Andrew Stubbs
2011-09-06 13:35 ` Andrew Stubbs
2011-09-09 12:48 ` Richard Earnshaw
2011-09-20 11:38 ` Andrew Stubbs
2011-10-13 15:08 ` Andrew Stubbs [this message]
2011-10-17 13:42 ` Richard Earnshaw
2011-10-18 14:43 ` Andrew Stubbs
2011-10-18 14:51 ` Richard Earnshaw
2011-10-18 15:19 ` Andrew Stubbs
2011-10-19 12:06 ` Andrew Stubbs
2011-08-29 8:37 ` Michael Hope
2011-08-30 12:22 ` Stubbs, Andrew
2011-08-30 21:36 ` Michael Hope
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=4E96F5D9.6090207@codesourcery.com \
--to=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=patches@linaro.org \
--cc=rearnsha@arm.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).