From: Michael Barker <mikeb01@gmail.com>
To: stephen@networkplumber.org
Cc: dev@dpdk.org, Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [PATCH v4] Add pragma to ignore gcc-compat warnings in clang when used with diagnose_if.
Date: Mon, 31 Jan 2022 13:08:21 +1300 [thread overview]
Message-ID: <CALwNKeRvdemYiHE_ow-xeEDdJqtACGNDoGX+w1Fv=JmMF_rqLg@mail.gmail.com> (raw)
In-Reply-To: <20220123155545.60de272f@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
> > extension [-Werror,-Wgcc-compat]
> > __rte_internal
> > ^
>
> Which clang version is this?
>
Clang 10, 11, 12 and 13.
> Perhaps the allow internal API could use a different attribute that
> could work in both cases?
>
I've realised I've made a small error. It is not -Wall that includes this
particular check, but -Wpendantic. I'll update the commit message.
However I can't find an attribute that is cross platform. There is the
#error directive, but it does not work as an attribute. I've also tried
adding `#if __clang__` around the macro as well, but the warning still gets
triggered by clang.
If there are any other options that I've missed, let me know and I can try
them out.
Mike.
[-- Attachment #2: Type: text/html, Size: 1663 bytes --]
next prev parent reply other threads:[~2022-01-31 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 23:14 [PATCH] " Michael Barker
2022-01-17 23:23 ` [PATCH v2] " Michael Barker
2022-01-20 14:16 ` Thomas Monjalon
2022-01-23 21:17 ` Michael Barker
2022-01-23 23:53 ` Stephen Hemminger
2022-01-23 21:07 ` [PATCH v3] " Michael Barker
2022-01-23 21:20 ` [PATCH v4] " Michael Barker
2022-01-23 23:55 ` Stephen Hemminger
2022-01-31 0:08 ` Michael Barker [this message]
2022-01-25 10:33 ` Ray Kinsella
2022-01-31 0:10 ` Michael Barker
2022-01-31 0:05 ` [PATCH v5] " Michael Barker
2022-02-12 14:00 ` Thomas Monjalon
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='CALwNKeRvdemYiHE_ow-xeEDdJqtACGNDoGX+w1Fv=JmMF_rqLg@mail.gmail.com' \
--to=mikeb01@gmail.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
--cc=stephen@networkplumber.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 NNTP newsgroup(s).