From: Ilija Kocho <ilijak@siva.com.mk>
To: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] eCos arm-eabi GNU tools - test release 4.6.3-20120315
Date: Mon, 19 Mar 2012 08:53:00 -0000 [thread overview]
Message-ID: <4F66F3D9.4040601@siva.com.mk> (raw)
In-Reply-To: <4F66EBDB.3010008@televic.com>
On 19.03.2012 09:18, Lambrecht Jürgen wrote:
> On 03/18/2012 05:08 PM, John Dallaway wrote:
>> I have generated a new test release of the GNU tools for ARM targets
>> based on GCC 4.6.3. The new test release avoids issues with GCC 4.6.2.
>> Ref:
>>
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001468#c30
>>
> I am testing 4.6.2 (AT91SAM9260 platform), and will try 4.6.3 to go on
> (ecos 3.0 builds OK, but our application fails).
> But when I want to see those "issues with GCC 4.6.2", I get this:
>
> You are not authorized to access bug #1001468.
>
> (I can see other bugs.)
> Why is this? Maybe something wrong with my account, because when I go to
There's nothing wrong with your account. This bug is for use by eCos
maintainers.
I apologize for inconvenience.
Below is a copy of the subject link that explains the reason for our
switch to 4.6.3.
Ilija
The comment: ================
Another serious bug in GCC 4.6.2
I have started playing with Cortex-M4 Floating Point Unit and found out that
conversion between float and double doesn't work when hardware floating point
is on: -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16
For instance:
{
double dbl;
float flo;
//.....
dbl = flo;
// dbl is rubish
}
It is due to wrong helper library and seem to be the following bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51835
I tried GCC 4.6.3 and it seems to work. I'll do some more tests but IMO we
should start considering of replacing current 4.6.2-20120125 test release with
something newer, possibly 4.6.3. Building of 4.6.3, as noted by Sergei, is quite straight-forward - I just applied the 4.6.2 patches.
Of course, until this is resolved nothing can stop us from hunting warnings
with current test release.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2012-03-19 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 16:08 John Dallaway
2012-03-19 8:19 ` Lambrecht Jürgen
2012-03-19 8:53 ` Ilija Kocho
2012-03-19 8:53 ` Ilija Kocho [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F66F3D9.4040601@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=J.Lambrecht@TELEVIC.com \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).