This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001468] eCos GNU tools 4.6.2
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Fri, 2 Mar 2012 16:19:31 +0000
- Subject: [Bug 1001468] eCos GNU tools 4.6.2
- Auto-submitted: auto-generated
- References: <bug-1001468-13@http.bugs.ecos.sourceware.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 #25 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-03-02 16:19:22 GMT ---
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?
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.
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 on the CC list for the bug.