From: Thiago Galesi <thiagogalesi@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crc32: remove useless __pure modifier from functions
Date: Mon, 2 Mar 2009 12:50:59 -0300 [thread overview]
Message-ID: <82ecf08e0903020750q3670de6u4162e4f01c847003@mail.gmail.com> (raw)
In-Reply-To: <1236007103.18284.83.camel@penberg-laptop>
Actually, the effects of most keywords (like const, etc) affect things
outside of the module (the callers)
http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Function-Attributes.html
has a good explanation.
Briefly, a _pure function only depends on its parameters and the only
return is via the function return, so the compiler can optimize some
of its calls away.
--
-
Thiago Galesi
On Mon, Mar 2, 2009 at 12:18 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> The pure attribute has absolutely no effect with GCC 4.2:
>
> text data bss dec hex filename
> 2456 0 0 2456 998 lib/crc32.o.old
> 2456 0 0 2456 998 lib/crc32.o.new
>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> lib/crc32.c | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/lib/crc32.c b/lib/crc32.c
> index 49d1c9e..9ff76ad 100644
> --- a/lib/crc32.c
> +++ b/lib/crc32.c
> @@ -49,7 +49,7 @@ MODULE_LICENSE("GPL");
> * @p: pointer to buffer over which CRC is run
> * @len: length of buffer @p
> */
> -u32 __pure crc32_le(u32 crc, unsigned char const *p, size_t len);
> +u32 crc32_le(u32 crc, unsigned char const *p, size_t len);
>
> #if CRC_LE_BITS == 1
> /*
> @@ -57,7 +57,7 @@ u32 __pure crc32_le(u32 crc, unsigned char const *p, size_t len);
> * simplified by inlining the table in ?: form.
> */
>
> -u32 __pure crc32_le(u32 crc, unsigned char const *p, size_t len)
> +u32 crc32_le(u32 crc, unsigned char const *p, size_t len)
> {
> int i;
> while (len--) {
> @@ -69,7 +69,7 @@ u32 __pure crc32_le(u32 crc, unsigned char const *p, size_t len)
> }
> #else /* Table-based approach */
>
> -u32 __pure crc32_le(u32 crc, unsigned char const *p, size_t len)
> +u32 crc32_le(u32 crc, unsigned char const *p, size_t len)
> {
> # if CRC_LE_BITS == 8
> const u32 *b =(u32 *)p;
> @@ -145,7 +145,7 @@ u32 __pure crc32_le(u32 crc, unsigned char const *p, size_t len)
> * @p: pointer to buffer over which CRC is run
> * @len: length of buffer @p
> */
> -u32 __pure crc32_be(u32 crc, unsigned char const *p, size_t len);
> +u32 crc32_be(u32 crc, unsigned char const *p, size_t len);
>
> #if CRC_BE_BITS == 1
> /*
> @@ -153,7 +153,7 @@ u32 __pure crc32_be(u32 crc, unsigned char const *p, size_t len);
> * simplified by inlining the table in ?: form.
> */
>
> -u32 __pure crc32_be(u32 crc, unsigned char const *p, size_t len)
> +u32 crc32_be(u32 crc, unsigned char const *p, size_t len)
> {
> int i;
> while (len--) {
> @@ -167,7 +167,7 @@ u32 __pure crc32_be(u32 crc, unsigned char const *p, size_t len)
> }
>
> #else /* Table-based approach */
> -u32 __pure crc32_be(u32 crc, unsigned char const *p, size_t len)
> +u32 crc32_be(u32 crc, unsigned char const *p, size_t len)
> {
> # if CRC_BE_BITS == 8
> const u32 *b =(u32 *)p;
> --
> 1.5.4.3
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-03-02 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 15:18 Pekka Enberg
2009-03-02 15:50 ` Thiago Galesi [this message]
2009-03-02 17:28 ` Pekka Enberg
2009-03-02 17:42 ` Thiago Galesi
2009-03-03 9:33 ` Will Newton
2009-03-03 13:17 ` Thiago Galesi
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=82ecf08e0903020750q3670de6u4162e4f01c847003@mail.gmail.com \
--to=thiagogalesi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®