Re: Mark bitrevX() functions as const

Akinobu Mita <[email protected]> wrote:

> __attribute_pure__ ?

I'm not sure "pure" is better than const in this case.  Although it *does* look
at a global variable (byte_rev_table), that variable is constant.  In effect,
the functions output does only depend on its input.  The R/O data it requires
is no different to its out of line code.  You'd have to consult a compiler
wrangler to be sure, though.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: Mark bitrevX() functions as const
    • From: Akinobu Mita <[email protected]>
  • Mark bitrevX() functions as const
    • From: David Howells <[email protected]>

• Prev by Date: Re: Status of buffered write path (deadlock fixes)
• Next by Date: Re: [PATCH] libata: don't initialize sg in ata_exec_internal() if DMA_NONE
• Previous by thread: Re: Mark bitrevX() functions as const
• Next by thread: Re: Mark bitrevX() functions as const
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]