The Linaro Toolchain Working Group is pleased to announce the latest
release of Linaro GCC 4.5.
Linaro GCC 4.5 is the fourth release in the 4.5 series. Based off the
latest GCC 4.5.1+svn164911, it includes many ARM-focused performance
improvements and bug fixes.
Interesting changes include:
* Va
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
The Linaro Toolchain Working Group is pleased to announce the release
of Linaro GDB 7.2.
Linaro GDB 7.2 2010.11-0 is the second release in the 7.2 series.
Based off the latest GDB 7.2, it includes a number of ARM-focused bug
fixes and enhancements.
This release concentrates on the GDB test suite
I agree on the approach. I'm concerned about moving over to SVN for a
few reasons: duplication of accounts (however most of the WG already
have or will need sourceware.org accounts), harder merging (with bzr
you do a 'bzr merge lp:gcc' and it does a good, three way merge with
trunk. Last time I u
On 8 November 2010 20:30, Chung-Lin Tang wrote:
> Still, I would like to see a 'linaro-trunk' branch under svn://
> gcc.gnu.org/svn/branches. It would actually serve a different purpose than
> a LP branch; the LP GCC 4.6 would probably eventually turn into Linaro 4.6,
> while a SVN branch would b
On 2010/11/8 下午 07:01, Andrew Stubbs wrote:
Here's my proposal:
* Create a new Launchpad branch for GCC 4.6.
* Synchronize this branch with upstream regularly
* once per week, perhaps.
* Try to get upstream approval for all new patches in the usual way
* on the understanding that
Mark Mitchell writes:
> On 11/8/2010 7:22 AM, Yao Qi wrote:
>> In this situation, this LP GCC 4.6 branch can be regarded as our
>> upstreams at that moment.
>>
>>> * Try to get upstream approval for all new patches in the usual way
>>>* on the understanding that they won't be applied until s
On 11/8/2010 7:22 AM, Yao Qi wrote:
> In this situation, this LP GCC 4.6 branch can be regarded as our
> upstreams at that moment.
>
>> * Try to get upstream approval for all new patches in the usual way
>>* on the understanding that they won't be applied until stage 1
>>* bug fixes are
On 11/08/2010 07:01 PM, Andrew Stubbs wrote:
> Hi all,
>
> As you may or may not know, upstream GCC has now entered 'stage 3' of
> it's development cycle. This will last until spring.
>
> This means that they are only accepting bug fixes and documentation
> improvements. New features and any perf
Hi all,
As you may or may not know, upstream GCC has now entered 'stage 3' of
it's development cycle. This will last until spring.
This means that they are only accepting bug fixes and documentation
improvements. New features and any performance improvements must wait
until GCC 4.6 branches,
10 matches
Mail list logo
