public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>
To: Yi-Hsiu Hsu <ahsu@marvell.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM] New CPU support for Marvell PJ4 cores
Date: Mon, 25 Jun 2012 20:03:00 -0000	[thread overview]
Message-ID: <CACUk7=VX0cmx2x+z9WYsnkPLKiDK7Db9S-kqQg0w3zbZayAOEQ@mail.gmail.com> (raw)
In-Reply-To: <689C75E0D210324F8BE88961219F681624B5BCD276@SC-VEXCH2.marvell.com>

On 20 June 2012 03:53, Yi-Hsiu Hsu <ahsu@marvell.com> wrote:
> marvell-pj4 is added to BE8_LINK_SPEC.
>
> Modified patch is attached.

Missing a modified changelog entry.


Ramana

>
> Thanks!
>
> B.R.
> Yi-Hsiu, Hsu
>
> -----Original Message-----
> From: Ramana Radhakrishnan [mailto:ramana.radhakrishnan@linaro.org]
> Sent: Thursday, June 14, 2012 2:19 AM
> To: Yi-Hsiu Hsu
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH, ARM] New CPU support for Marvell PJ4 cores
>
> On 29 May 2012 10:07, Yi-Hsiu Hsu <ahsu@marvell.com> wrote:
>> Hi,
>>
>> This patch maintains Marvell PJ4 cores pipeline description.
>> Run arm testsuite on arm-linux-gnueabi and no extra regressions are found.
>>
>>        * config/arm/marvell-pj4.md: New marvell-pj4 pipeline description.
>>        * config/arm/arm.c (arm_issue_rate): Add marvell_pj4.
>>        * config/arm/arm-cores.def: Add core marvell-pj4.
>>        * config/arm/arm-tune.md: Regenerated.
>>        * config/arm/arm-tables.opt: Regenerated.
>>        * doc/invoke.texi: Added entry for marvell-pj4.
>
> This command line option should also be added to BE8_LINK_SPEC similar
> to what's done for the other v7-a cores.
>
> Ok with that change.
>
> regards,
> Ramana
>
>
>
>>
>>
>> Thanks!
>>
>> P.S. I create the patch from revision 187308, but this revision is unable to build successfully, then I apply this patch to revision 187623 and successfully build and pass the testsuite.
>>

  reply	other threads:[~2012-06-25 19:36 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 [this message]
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
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='CACUk7=VX0cmx2x+z9WYsnkPLKiDK7Db9S-kqQg0w3zbZayAOEQ@mail.gmail.com' \
    --to=ramana.radhakrishnan@linaro.org \
    --cc=ahsu@marvell.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).