diff options
author | Kumar Gala <galak@kernel.crashing.org> | 2008-07-30 08:01:15 -0500 |
---|---|---|
committer | Wolfgang Denk <wd@denx.de> | 2008-07-31 11:21:15 +0200 |
commit | 57c219ad5d34dd9d49991777a62e3899595f2ec7 (patch) | |
tree | d2c7f14906580e9583d948527de782ed7d8b5936 /board/freescale/mpc8568mds | |
parent | 3f9ae1a5d43c49a8ecf497470c3d1d80255e44b9 (diff) | |
download | u-boot-imx-57c219ad5d34dd9d49991777a62e3899595f2ec7.zip u-boot-imx-57c219ad5d34dd9d49991777a62e3899595f2ec7.tar.gz u-boot-imx-57c219ad5d34dd9d49991777a62e3899595f2ec7.tar.bz2 |
Fix compile warnings in dlmalloc
The origional code was using on odd reference to get to the first
real element in av_[]. The first two elements of the array are
not used for actual bins, but for house keeping. If we are more
explicit about how use the first few elements we can get rid of the
warnings:
dlmalloc.c: In function 'malloc_extend_top':
dlmalloc.c:1971: warning: dereferencing type-punned pointer will break strict-aliasing rules
dlmalloc.c:1999: warning: dereferencing type-punned pointer will break strict-aliasing rules
dlmalloc.c:2029: warning: dereferencing type-punned pointer will break strict-aliasing rules
...
The logic of how this code came to be is:
bin_at(0) = (char*)&(av_[2]) - 2*SIZE_SZ
SIZE_SZ is the size of pointer, and av_ is arry of pointers so:
bin_at(0) = &(av_[0])
Going from there to bin_at(0)->fd or bin_at(0)->size should be straight forward.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'board/freescale/mpc8568mds')
0 files changed, 0 insertions, 0 deletions