mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux@MichaelGeng.de (Michael Geng)
Cc: linux-kernel@vger.kernel.org, kraxel@bytesex.org
Subject: Re: [ANNOUNCE] new driver for teletext decoder SAA5246A
Date: Wed, 25 Feb 2004 13:36:47 -0800	[thread overview]
Message-ID: <20040225133647.1a9a3231.akpm@osdl.org> (raw)
In-Reply-To: <20040225181041.GA2446@t-online.de>

linux@MichaelGeng.de (Michael Geng) wrote:
>
> No, it doesn't shrink. I already tested that when I developed 
> the driver with saa5249.c as a template. Now I made a completely
> inline-free version, but /usr/bin/size shows exactly the same
> size. By the way, this shows that gcc does a good job. Of course
> this could also depend on the architecture, but on my Pentium 4
> box gcc really puts the inline parts inline.

Yup.  I was suggesting remmoval of the `inline' keyword, rather than
actually moving the bodies of those functions into the caller.

I've previously seen significant code size reductions by _not_ inlining
large functions which had a single call site - just leave them as normal
out-of-line functions.  So it worth experimenting with - pretty simple to
do.  But if you're using a recent gcc it's probably inlining the function
even when it's not marked inline.   Whatever.

> If you want to add the patch, how about the following changelog:
> 
> [V4L]: Added new driver for Teletext decoder SAA5246A from Philips

Thanks.

  reply	other threads:[~2004-02-25 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 11:34 Michael Geng
     [not found] ` <20040225041330.51961b28.akpm@osdl.org>
2004-02-25 18:10   ` Michael Geng
2004-02-25 21:36     ` Andrew Morton [this message]
2004-02-25 22:29       ` Michael Geng
     [not found] ` <403CFBD9.2000607@convergence.de>
2004-02-25 21:11   ` Michael Geng

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=20040225133647.1a9a3231.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@MichaelGeng.de \
    /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®