From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] GCC4.4: Squash multiple warnings due to strict aliasing
Date: Mon, 26 Sep 2011 20:35:25 +0200 [thread overview]
Message-ID: <201109262035.25445.marek.vasut@gmail.com> (raw)
In-Reply-To: <20110926183358.2A9441407999@gemini.denx.de>
On Monday, September 26, 2011 08:33:58 PM Wolfgang Denk wrote:
> Dear Marek Vasut,
>
> In message <201109261937.01263.marek.vasut@gmail.com> you wrote:
> > > What exactly are the advantages, and what the disadvantages?
> > >
> > > code size / memory footprint?
> >
> > I assume converting those to inline function will yield no memory usage
> > growth at all.
>
> Please don't assume, measure it. Thanks.
Will do ... though I'd prefer to have this patch and the other one separate.
Cheers
>
> Best regards,
>
> Wolfgang Denk
prev parent reply other threads:[~2011-09-26 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 2:06 [U-Boot] [PATCH] GCC4.4: Squash multiple warnings due to strict aliasing Marek Vasut
2011-09-26 9:26 ` Nick Thompson
2011-09-26 9:32 ` Marek Vasut
2011-09-26 9:44 ` Nick Thompson
2011-09-26 9:48 ` Marek Vasut
2011-09-26 11:30 ` Wolfgang Denk
2011-09-26 17:37 ` Marek Vasut
2011-09-26 18:33 ` Wolfgang Denk
2011-09-26 18:35 ` Marek Vasut [this message]
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=201109262035.25445.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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 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.