On 09.11.2010 14:05, Andrew Stubbs wrote:
On 09/11/10 06:51, Michael Hope wrote:
I've been going through the ChangeLog for the release and am having
trouble justifying some of the changes brought in. In particular:
* -fstrict-volatile-bitfields, which is more appropriate for bare
metal/kernel co
On 09/11/10 06:51, Michael Hope wrote:
I've been going through the ChangeLog for the release and am having
trouble justifying some of the changes brought in. In particular:
* -fstrict-volatile-bitfields, which is more appropriate for bare
metal/kernel code
* Cortex-M4 support
* C locale su
On 11/09/2010 02:51 PM, Michael Hope wrote:
>
> Our focus is time based performance on the Cortex-A series with an
> implied applications over kernel/bare metal. This is a very narrow
> view, but every non-performance line of code we bring in can also
> bring in a bug.
>
Can we explain this cri
I've been going through the ChangeLog for the release and am having
trouble justifying some of the changes brought in. In particular:
* -fstrict-volatile-bitfields, which is more appropriate for bare
metal/kernel code
* Cortex-M4 support
* C locale support in libstdc++-v3
The march/mcpu clean
