From: Robert Love <rml@tech9.net>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deprecated function attribute
Date: 28 Dec 2002 15:50:12 -0500 [thread overview]
Message-ID: <1041108612.948.22.camel@icbm> (raw)
In-Reply-To: <20021228185355.GA22304@nevyn.them.org>
On Sat, 2002-12-28 at 13:53, Daniel Jacobowitz wrote:
> > If we want to be preemptive, we can rename the above to "__deprecated__"
> > but I think plain "deprecated" is much better looking.
>
> Eek, please call it something else - something that looks visibly like
> a syntax rather than a name. __deprecated or __deprecated__ or
> DEPRECATED.
Like I said, that is fine with me...
Attached. Still untested :-)
Robert Love
compiler.h | 13 +++++++++++++
1 files changed, 13 insertions(+)
diff -urN linux-2.5.53/include/linux/compiler.h linux/include/linux/compiler.h
--- linux-2.5.53/include/linux/compiler.h 2002-12-28 12:38:56.000000000 -0500
+++ linux/include/linux/compiler.h 2002-12-28 12:45:03.000000000 -0500
@@ -13,6 +13,19 @@
#define likely(x) __builtin_expect((x),1)
#define unlikely(x) __builtin_expect((x),0)
+/*
+ * Allow us to mark functions as 'deprecated' and have gcc emit a nice
+ * warning for each use, in hopes of speeding the functions removal.
+ * Usage is:
+ * int deprecated foo(void)
+ * and then gcc will emit a warning for each usage of the function.
+ */
+#if __GNUC__ == 3
+#define __deprecated__ __attribute__((deprecated))
+#else
+#define __deprecated__
+#endif
+
/* This macro obfuscates arithmetic on a variable address so that gcc
shouldn't recognize the original var, and make assumptions about it */
#define RELOC_HIDE(ptr, off) \
next prev parent reply other threads:[~2002-12-28 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 0:57 [PATCH] Mark deprecated functions so they give a warning on use Rusty Russell
2002-12-28 5:54 ` Richard Henderson
2002-12-28 15:30 ` Alexander Kellett
2002-12-28 17:51 ` [PATCH] deprecated function attribute Robert Love
2002-12-28 18:03 ` Robert Love
2002-12-28 18:53 ` Daniel Jacobowitz
2002-12-28 20:50 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-28 23:32 william stinson
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=1041108612.948.22.camel@icbm \
--to=rml@tech9.net \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.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.