All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Måns Rullgård" <mans@mansr.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Use ARCH_USE_BUILTIN_BSWAP.
Date: Tue, 29 Sep 2015 14:09:09 +0200	[thread overview]
Message-ID: <20150929120908.GB2505@linux-mips.org> (raw)
In-Reply-To: <yw1x612tqvur.fsf@unicorn.mansr.com>

On Tue, Sep 29, 2015 at 12:59:56PM +0100, Måns Rullgård wrote:

> Ralf Baechle <ralf@linux-mips.org> writes:
> 
> > On Tue, Sep 29, 2015 at 12:28:55PM +0200, Ralf Baechle wrote:
> >
> >>    text    data     bss     dec     hex filename
> >> 3996071  155804   88992 4240867  40b5e3 vmlinux         ip22 baseline
> >> 3985687  159900   88992 4234579  409d53 vmlinux         ip22 + bswap patch
> >> 6913157  378552  251024 7542733  7317cd vmlinux         ip27 baseline
> >> 6878581  378552  251024 7508157  7290bd vmlinux         ip27 + bswap patch
> >> 5773777  268752  187424 6229953  5f0fc1 vmlinux         malta baseline
> >> 5773401  268752  187424 6229577  5f0e49 vmlinux         malta + bswap patch
> >
> > A still unexplained effect of this patch and the reason why I have not
> > committed this patch is the increase of the data size for the ip22
> > configuration by 4096 bytes.  There is no change in data size expected.
> > Also this affects only the test with ip22_defconfig not any of the others
> > I've tried.
> 
> Have you checked which object file(s) the increase comes from?

Working on that.

  Ralf

  reply	other threads:[~2015-09-29 12:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 10:28 [PATCH] MIPS: Use ARCH_USE_BUILTIN_BSWAP Ralf Baechle
2015-09-29 11:52 ` Ralf Baechle
2015-09-29 11:59   ` Måns Rullgård
2015-09-29 12:09     ` Ralf Baechle [this message]
2015-09-29 13:28     ` Ralf Baechle
2015-09-29 13:34       ` Måns Rullgård
2015-09-29 14:27         ` Ralf Baechle

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=20150929120908.GB2505@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mans@mansr.com \
    /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.