DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>,
	 "jerinj@marvell.com" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
	 Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] eal/arm: remove CASP constraints for GCC
Date: Fri, 11 Feb 2022 08:53:36 +0100	[thread overview]
Message-ID: <CAJFAV8w4YJgD0TF3pxxPuONUeutCZSpCXQDDA+z-69eCkJ_uOw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x70fGU0QJzrRk48zqoxu8KKLXRi08g8UcjwVEi36-wLQ@mail.gmail.com>

On Tue, Nov 16, 2021 at 3:56 PM David Marchand
<david.marchand@redhat.com> wrote:
> > > GCC now assigns even register pairs for CASP, the fix has also been
> > > backported to all stable releases of older GCC versions.
> > > Removing the manual register allocation allows GCC to inline the functions
> > > and pick optimal registers for performing CASP.
> > >
> > > Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> > Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
>

I added a reference to gcc commit and applied, thanks.


-- 
David Marchand


      parent reply	other threads:[~2022-02-11  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 10:03 [dpdk-dev] [RFC] " pbhagavatula
2021-10-18  6:39 ` Ruifeng Wang
2021-11-05  8:57 ` [dpdk-dev] [PATCH v2] " pbhagavatula
2021-11-08  7:15   ` Ruifeng Wang
2021-11-16 14:56     ` David Marchand
2022-01-20 15:32       ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-02-11  7:53       ` David Marchand [this message]

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=CAJFAV8w4YJgD0TF3pxxPuONUeutCZSpCXQDDA+z-69eCkJ_uOw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=nd@arm.com \
    --cc=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    /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 NNTP newsgroup(s).