DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>
Subject: RE: [EXTERNAL] [PATCH v2] drivers/net: use intrinsic to access content of __m128i
Date: Wed, 5 Feb 2025 04:50:28 +0000	[thread overview]
Message-ID: <MW4PR18MB5244483B1E4E5BC7D58A452EA6F72@MW4PR18MB5244.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1735348983-19590-1-git-send-email-andremue@linux.microsoft.com>



>-----Original Message-----
>From: Andre Muezerie <andremue@linux.microsoft.com>
>Sent: Saturday, December 28, 2024 6:53 AM
>To: andremue@linux.microsoft.com
>Cc: bruce.richardson@intel.com; dev@dpdk.org;
>konstantin.v.ananyev@yandex.ru; Vamsi Krishna Attunuru
><vattunuru@marvell.com>
>Subject: [EXTERNAL] [PATCH v2] drivers/net: use intrinsic to access content of
>__m128i
>
>Compiler intrinsics should be used to access/manipulate contents of __m128i.
>Existing code results in the error below when compiled with MSVC:
>.. /drivers/net/octeon_ep/cnxk_ep_rx_sse. c(61): error C2440: 'type cast':
>cannot convert from '__m128i'
>
>Compiler intrinsics should be used to access/manipulate contents of __m128i.
>Existing code results in the error below when compiled with MSVC:
>
>../drivers/net/octeon_ep/cnxk_ep_rx_sse.c(61): error C2440:
>    'type cast': cannot convert from '__m128i' to 'rte_xmm_t'
>
>The fix is to use an intrinsic instead. This compiles fine with gcc, clang and
>msvc.
>
>Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>

Acked-by: Vamsi Attunuru <vattunuru@marvell.com>

  reply	other threads:[~2025-02-05  4:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 19:44 [PATCH] " Andre Muezerie
2024-12-28  1:23 ` [PATCH v2] " Andre Muezerie
2025-02-05  4:50   ` Vamsi Krishna Attunuru [this message]
2025-02-05 16:50     ` [EXTERNAL] " Jerin Jacob

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=MW4PR18MB5244483B1E4E5BC7D58A452EA6F72@MW4PR18MB5244.namprd18.prod.outlook.com \
    --to=vattunuru@marvell.com \
    --cc=andremue@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.v.ananyev@yandex.ru \
    /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).