From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] help with warnings and gcc-4.3.0
Date: Thu, 29 May 2008 11:44:11 -0500 [thread overview]
Message-ID: <20080529164411.GA2812@loki.buserror.net> (raw)
In-Reply-To: <33BB2AE6-1031-4381-8D4A-BE7E22E15369@kernel.crashing.org>
On Thu, May 29, 2008 at 11:31:28AM -0500, Kumar Gala wrote:
> #define bin_at(i) ((mbinptr)((char*)&(av_[2*(i) + 2]) - 2*SIZE_SZ))
> #define next_bin(b) ((mbinptr)((char*)(b) + 2 * sizeof(mbinptr)))
> #define prev_bin(b) ((mbinptr)((char*)(b) - 2 * sizeof(mbinptr)))
> ..
>
> #define top (bin_at(0)->fd) /* The topmost chunk */
> #define last_remainder (bin_at(1)) /* remainder from last split */
>
>
> but I can't seem to do anything to bin_at() to make them stop. Was
> wondering if anyone had any suggestions.
We could compile that file with -fno-strict-aliasing, which is probably
warranted anyway for the kind of pointer manipulation that malloc needs to
do.
-Scott
prev parent reply other threads:[~2008-05-29 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 16:31 [U-Boot-Users] help with warnings and gcc-4.3.0 Kumar Gala
2008-05-29 16:44 ` Scott Wood [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=20080529164411.GA2812@loki.buserror.net \
--to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox