DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com,
	bruce.richardson@intel.com, stephen@networkplumber.org,
	drc@linux.vnet.ibm.com
Subject: Re: [dpdk-dev] [PATCH] eal: standard c++ forbids defining the keyword asm as a macro
Date: Wed, 24 Mar 2021 14:55:48 -0700	[thread overview]
Message-ID: <20210324215548.GA2272@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <11634428.8dEGKDZn2b@thomas>

On Wed, Mar 24, 2021 at 06:52:40PM +0100, Thomas Monjalon wrote:
> 24/03/2021 18:28, Tyler Retzlaff:
> > 
> > so to qualify. you mean maybe it is breaking compilation of c++ in a
> > compiler that explicitly violates c++ standard when compiling c++? that
> > would mean it is not a c++ compiler.
> 
> The asm keyword is part of all C++ standards?
> It seems asm is non-standard in C,
> that's why we use __asm__.

the keyword is standard the meaning of the keyword is implementation
defined for both C and C++. though the C11 standard describes a
"common implementation is via statement of the form ..." [J.5.10]

> > in general i don't think it is a good practice to have dpdk introduce
> > names into the application namespace unqualified, but the point you make
> > is valid it can break c++ compilation if something was using this macro
> > as a convenience to the compiler specific extension __asm__. there will
> > be further issues with varying syntaxes that __asm__-style extensions
> > take from compiler to compiler as well.
> 
> Yes we need to make sure there is no specific extension involved.
> Is C++ asm the same as the C __asm__?

i don't think I can answer that as it depends on the compiler. there may
be no implementation at all or different implementations for asm or __asm__.
so basically neither form is portable (for an arch). though for __asm__
probably there is de-facto standardization around what gcc does and clang
mimics.

> > would you prefer that i change the preprocessor protection to include only
> > windows? since i'm certain that this will break for any c++ compiler on
> > windows the moment any stl header is included.
> 
> No, C++ is probably the right scope.
> 
> I don't know yet. I would like to understand the global picture,
> and have it properly documented in this commit log.

yep, no problem. i suspect we are probably the only ones using c++ and
dpdk (though others can speak up if they do too) which may be why this
has gone unnoticed until now.


  parent reply	other threads:[~2021-03-24 21:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  4:26 Tyler Retzlaff
2021-03-24  8:30 ` Thomas Monjalon
2021-03-24 16:45   ` Tyler Retzlaff
2021-03-24 17:04     ` Thomas Monjalon
2021-03-24 17:28       ` Tyler Retzlaff
2021-03-24 17:52         ` Thomas Monjalon
2021-03-24 19:52           ` Stephen Hemminger
2021-03-24 21:58             ` Tyler Retzlaff
2021-03-24 21:55           ` Tyler Retzlaff [this message]
2021-03-24 22:41             ` Dmitry Kozlyuk
2021-03-25  0:09               ` Tyler Retzlaff
2021-03-25  8:00                 ` Thomas Monjalon
2021-03-25 18:50                   ` Tyler Retzlaff
2021-04-13 13:10                     ` Thomas Monjalon
2021-04-13 13:35 ` Thomas Monjalon
2021-04-17  1:16   ` Tyler Retzlaff

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=20210324215548.GA2272@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=stephen@networkplumber.org \
    --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).