Re: 11.0-CURRENT (r292413) on a rpi2b: arm-gnueabi-freebsd/bin/ar, _fseeko, and memset vs memory alignment (SCTRL bit[1]=1?): Explains the Bus error?

On 2015-Dec-26, at 9:00 AM, Ian Lepore wrote: > On Fri, 2015-12-25 at 17:21 -0800, Mark Millard wrote: >> In my view "-mno-unaligned-access" is an even bigger hammer than I >> used. I find no clang statement about what its ABI consequences would >> be, unlike for what I did:

Re: 11.0-CURRENT (r292413) on a rpi2b: arm-gnueabi-freebsd/bin/ar, _fseeko, and memset vs memory alignment (SCTRL bit[1]=1?): Explains the Bus error?

Thanks, it sounds like I fixed a bug, but there’s more. What were the specific port so I can test it here? And to be clear, this is a buildworld on the RPi 2 using the cross-built world with CPUTYPE=armv7a or some such, right? Warner > On Dec 25, 2015, at 9:32 PM, Mark Millard

Re: 11.0-CURRENT (r292413) on a rpi2b: arm-gnueabi-freebsd/bin/ar, _fseeko, and memset vs memory alignment (SCTRL bit[1]=1?): Explains the Bus error?

On Fri, 2015-12-25 at 17:21 -0800, Mark Millard wrote: > In my view "-mno-unaligned-access" is an even bigger hammer than I > used. I find no clang statement about what its ABI consequences would > be, unlike for what I did: What mix of more padding for alignment vs. > more but smaller accesses?