This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001468] eCos GNU tools 4.6.2


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

--- Comment #27 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-03-03 14:30:11 GMT ---
(In reply to comment #26)
> > 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.

Agreed. But if that will be really needed. I would trust the eCosCentric
test results for ARM7 target.

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

It's clear. I did not suggest to follow all next 4.6 derivatives.

> > 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.

Good to know.

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

Today I tested a bit and GCC 4.6.3 based build (just for case)
http://ecos.sourceware.org/ml/ecos-devel/2012-03/msg00002.html

And as I told I had no problems with the contributed toolchain too,
though, my test "farm" is a very little farm (1-board stall), so, I
decided to point on that bug-fix here.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]