public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: ramrad01@arm.com, ahsu@marvell.com,
		gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM] New CPU support for Marvell PJ4 cores
Date: Mon, 21 Jan 2013 06:15:00 -0000	[thread overview]
Message-ID: <CAHFci29+obJ6VPAapwpxk=kErBp+wcOwRDeLqAGaBqV4ZTC8kA@mail.gmail.com> (raw)
In-Reply-To: <50FC5548.4000507@ubuntu.com>

On Mon, Jan 21, 2013 at 4:36 AM, Matthias Klose <doko@ubuntu.com> wrote:
> Am 18.01.2013 15:28, schrieb Ramana Radhakrishnan:
>> On 06/20/12 03:53, Yi-Hsiu Hsu wrote:
>>> marvell-pj4 is added to BE8_LINK_SPEC.
>>
>> Sorry about the time it's taken to finish this patch up. I seem to have missed
>> this one in the review process.
>>
>> I've now applied the attached patch after taking into account the recent
>> attribute changes and treated alu_reg and simple_alu_imm as you have treated
>> alu, rebased to trunk to fix up some small issues with BE8_LINK_SPECS.
>>
>> Additionally I've removed tune_marvell as that seems redundant at this point of
>> time - an additional attribute and testing that appears to be unnecessary
>> instead of just one more inequality test.
>>
>> The only part I'm not sure about is how to treat the simple_alu_shift category
>> here , so a patch to handle them in the pj4 pipeline description would be welcome.
>>
>>
>> Thanks
>> Ramana
>>
>> 2013-01-18  Yi-Hsiu Hsu  <ahsu@marvell.com>
>>             Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>
>>
>>         * config/arm/marvell-pj4.md: New file.
>>         * config/arm/arm.c (arm_issue_rate): Add marvell_pj4.
>>         * config/arm/arm.md (generic_sched): Add marvell_pj4.
>>         (generic_vfp): Likewise.
>>         * config/arm/arm-cores.def: Add marvell-pj4.
>>         * config/arm/arm-tune.md: Regenerate.
>>         * config/arm/arm-tables.opt: Regenerate.
>>         * config/arm/bpabi.h (BE8_LINK_SPEC): Add marvell_pj4.
>>         * doc/invoke.texi: Document marvell-pj4.
>>
>>>
>>> Modified patch is attached.
>
> the patch was missing the new file config/arm/marvell-pj4.md. Checked is as
> obvious to restore the bootstrap.
>
>   Matthias
>

Checkin R195295 for this patch causes build failure for arm-none-eabi.
Please see PR56058.

--
Best Regards.

  reply	other threads:[~2013-01-21  6:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29  9:09 Yi-Hsiu Hsu
2012-06-13 18:33 ` Ramana Radhakrishnan
2012-06-14  7:47   ` Chung-Lin Tang
2012-06-20  3:52   ` Yi-Hsiu Hsu
2012-06-25 20:03     ` Ramana Radhakrishnan
2012-06-26  2:14       ` Yi-Hsiu Hsu
2012-06-26  5:51         ` Chung-Lin Tang
2012-06-26  7:46           ` Yi-Hsiu Hsu
2012-09-07  6:31           ` PING: " Yi-Hsiu Hsu
2012-11-30  4:44           ` Yi-Hsiu Hsu
2013-01-18 14:28     ` Ramana Radhakrishnan
2013-01-20 20:36       ` Matthias Klose
2013-01-21  6:15         ` Bin.Cheng [this message]
2013-01-21 10:00         ` Ramana Radhakrishnan
2013-01-21  8:52       ` Yi-Hsiu Hsu
2013-01-21 10:56         ` Ramana Radhakrishnan
2013-01-22  0:44           ` Yi-Hsiu Hsu

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='CAHFci29+obJ6VPAapwpxk=kErBp+wcOwRDeLqAGaBqV4ZTC8kA@mail.gmail.com' \
    --to=amker.cheng@gmail.com \
    --cc=ahsu@marvell.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ramrad01@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).