DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org
Subject: Re: RTE_MARKER with MSVC
Date: Mon, 26 Feb 2024 09:43:53 -0800	[thread overview]
Message-ID: <20240226174353.GA23463@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F265@smartserver.smartshare.dk>

On Sat, Feb 24, 2024 at 12:16:58PM +0100, Morten Brørup wrote:
> Hi Tyler,
> 
> Does MSVC permit empty structures, i.e. structures with no fields? Perhaps with some additional decoration, a la [[msvc::no_unique_address]].
> If so, perhaps that would be a possible workaround for RTE_MARKERs.

i had some pretty long conversations with one of the main msvc devs
about this and they couldn't identify anything that they had that could
be used.

we didn't exhaustively dig through new versions of the standards but
even if there was something there we probably couldn't use it while
still baselined to C11.

i know the inline accessors were not going to be a perfect solution
either for the reason you raise on list. at this point i'm trying to
find a happy medium to solve the problem where everyone doesn't end up
too upset.

even anonymous unions turn out to be an imperfect solution because
there's a corner case they can't cover where the union ends up with a
field that is a FAM.

i even asked if they could just support similar as an extension but they
were pretty firm no. at this point unless enhancements are absolute need
i am not likely to get large investments from msvc (for now). i've spent
an enormous amount of their resources in the last couple of years for
dpdk and they want to see some customers using dpdk before they are able
to commit more.

fortunately i think we have enough now to at least get customers using
dpdk without significant compromises (assuming i can ever get all my
changes upstream).

also in case i haven't said it lately, i appreciate all the review and
input you've given it really helps a lot.

ty


> 
> 
> Med venlig hilsen / Kind regards,
> -Morten Brørup
> 

      reply	other threads:[~2024-02-26 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 11:16 Morten Brørup
2024-02-26 17:43 ` Tyler Retzlaff [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=20240226174353.GA23463@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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 NNTP newsgroup(s).