[Bug 1001468] eCos GNU tools 4.6.2

[bugzilla-daemon at bugs dot ecos dot sourceware dot org]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001468

--- Comment #26 from Ilija Kocho <ilijak@siva.com.mk> 2012-03-03 13:47:31 GMT ---
(In reply to comment #25)
> 2012/03/01 GCC 4.6.3 released (http://sourceware.org/gcc/)
> 
> As they said GCC 4.6.3 is a bug-fix release for GCC 4.6.2.
> 
> I looked at its PR list
> 
>  
> http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.6.3
> 
> Well, in main I search for /arm bug-fix reports. My concern is a bug
> 
>   http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49641
> 
> This bug exists (not fixed) in GCC 4.6.2. Should we apply a proposal
> patch to our new arm-eabi toolchain (4.6.2 based)? What is your opinion? 

If the bug is so severe that we must have a fix, considering that we're just
beginning with 4.6, I would consider 4.6.3 rather than a patch.

Otherwise there will be 4.6.minors in future an we can't follow them all.

> 
> FYI 
> 
> Good news that I did not meet such gas warnings when I tested GCC 4.6.2
> on my board, bad ones that it is possible to get it for other targets,
> or ARM7 (armv4) cpus.
> 
> I just s/4.6.2/4.6.3/ for my build script and it was possible to build
> arm-eabi toolchain (4.6.3). There were no hunks/fails for used patches.

Probably the same patches will be applicable without hunk-fails to any
4.6.minor. FYI they stem back from 4.6.0.


> However, I have not tested yet new toolchain on real hardware.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.