From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] liburcu: likely and unlikely macro collision
Date: Tue, 1 Nov 2011 18:00:18 -0400 [thread overview]
Message-ID: <20111101220018.GA19730@Krystal> (raw)
In-Reply-To: <CAEoG=qO4XivFb9XAkrefF3boVP9uZZYW2ncRKpKvxm6VpZsmyw@mail.gmail.com>
Hi,
likely()/unlikely() seems to be amongst the last macros that urcu
defines that don't have urcu-specific prefixes. Thoughts on whether we
should add a prefix such as caa_likely() and caa_unlikely() are welcome.
Thanks,
Mathieu
* Rafael Fernandez (rfernan3 at illinois.edu) wrote:
> Hi Matthieu,
>
> I am trying to incorporate liburcu in a project I am working with.
> Unfourtunately there are several collisions of the definitions of
> likely and unlikely. Would it be possible for you to add a prefix to
> the macros such that there aren't any collisions? I think it would be
> cleaner/easier for future users to incorporate into existing code
> bases.
>
> Thank you,
> Rafael
>
> --
> Rafael E. Fern?ndez
> B.S. Computer Science
> University of Illinois at Urbana-Champaign
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next parent reply other threads:[~2011-11-01 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEoG=qO4XivFb9XAkrefF3boVP9uZZYW2ncRKpKvxm6VpZsmyw@mail.gmail.com>
2011-11-01 22:00 ` Mathieu Desnoyers [this message]
2011-11-01 23:05 ` Stephen Hemminger
2011-11-01 23:55 ` Mathieu Desnoyers
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=20111101220018.GA19730@Krystal \
--to=mathieu.desnoyers@efficios.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