All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 745] performance-thread build failure with clang 12.0.1
Date: Sun, 20 Jun 2021 12:04:01 +0000	[thread overview]
Message-ID: <bug-745-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=745

            Bug ID: 745
           Summary: performance-thread build failure with clang 12.0.1
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

"""
$ meson --werror -Dexamples=all build && ninja-build -C build
...
...
../examples/performance-thread/pthread_shim/main.c:75:2: error: 'pthread_yield'
is deprecated: pthread_yield is deprecated, use sched_yield instead
[-Werror,-Wdeprecated-declarations]
        pthread_yield();
        ^
/usr/include/pthread.h:478:3: note: 'pthread_yield' has been explicitly marked
deprecated here
  __attribute_deprecated_msg__ ("\
  ^
/usr/include/sys/cdefs.h:292:19: note: expanded from macro
'__attribute_deprecated_msg__'
         __attribute__ ((__deprecated__ (msg)))
"""

Reproduces on main (8050b61).

OS: Fedora 35 (rawhide)
meson: 0.58.0
ninja-build: 1.10.2
clang: 12.0.1 (Fedora 12.0.1~rc1-3.fc35)

clang version 12.0.0 in Fedora 34 doesn't reproduce.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-06-20 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20 12:04 bugzilla [this message]
2021-08-16 13:56 ` [dpdk-dev] [Bug 745] performance-thread build failure with clang 12.0.1 bugzilla

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=bug-745-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.