public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] lib/decompress_unxz.c: removing all memory helper functions
Date: Thu, 24 May 2012 10:40:29 -0700	[thread overview]
Message-ID: <1337881229.5070.29.camel@joe2Laptop> (raw)
In-Reply-To: <4FBE6FF6.5090904@zytor.com>

On Thu, 2012-05-24 at 10:29 -0700, H. Peter Anvin wrote:
> On 05/24/2012 10:26 AM, Joe Perches wrote:
> > On Thu, 2012-05-24 at 10:03 -0600, T Makphaibulchoke wrote:
> >> The patch cleans up the file lib/decompress_unxz.c by removing all memory
> >> helper functions, e.g., memmove.  By doing so, any architecture's preboot
> >> environment supporting the XZ decompression needs to define its own copy of
> >> any of the missing memory helper functions.
> > 
> > Perhaps a silly question, but why not use
> > the __builtin variants?
> 
> For a lot of cases the __builtin variants just generate a call to the
> expected out-of-line function, so you need it anyway.

While I'm not completely knowledgeable about gcc,
aren't all the __builtin_mem<foo> functions always
available in gcc 3+

http://gcc.gnu.org/onlinedocs/gcc-3.0.4/gcc_5.html#SEC114

It does say:

Many of these functions are only optimized in certain cases; if not
optimized in a particular case, a call to the library function will be
emitted.

  reply	other threads:[~2012-05-24 17:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 16:03 [PATCH] lib/decompress_unxz.c: removing all memory helper functions T Makphaibulchoke
2012-05-24 17:26 ` Joe Perches
2012-05-24 17:29   ` H. Peter Anvin
2012-05-24 17:40     ` Joe Perches [this message]
2012-05-24 17:41       ` H. Peter Anvin
2012-05-24 17:50         ` Joe Perches
2012-05-24 17:56           ` H. Peter Anvin
2012-05-25  8:34 ` Lasse Collin
2012-05-25 16:31   ` Thavatchai Makphaibulcboke
2012-05-25 17:05     ` Thavatchai Makphaibulcboke
2012-05-25 17:13       ` H. Peter Anvin
2012-05-25 19:35     ` Lasse Collin
2012-05-28  7:03 ` Jean-Christophe PLAGNIOL-VILLARD
2012-06-01  2:48   ` Thavatchai Makphaibulcboke
2012-06-01  2:54     ` Joe Perches
2012-06-01  3:38     ` H. Peter Anvin
2012-06-01 18:37       ` Thavatchai Makphaibulcboke
2012-06-01 18:46         ` H. Peter Anvin
2012-06-01 18:58           ` Thavatchai Makphaibulcboke

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=1337881229.5070.29.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox