From: Ilija Kocho <ilijak@siva.com.mk>
To: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
Cc: Alex Schuilenburg <alexs@ecoscentric.com>,
"ecos-devel@ecos.sourceware.org"
<ecos-devel@ecos.sourceware.org>,
John Dallaway <john@dallaway.org.uk>,
Jonathan Larmour <jifl@jifvik.org>
Subject: Re: eCos GNU tools 4.6.3-20120315 [Was Re: eCos GNU tools 4.6.2-20120125 ready for testing]
Date: Wed, 04 Apr 2012 13:18:00 -0000 [thread overview]
Message-ID: <4F7C4A0C.40200@siva.com.mk> (raw)
In-Reply-To: <4F7C453B.8080107@televic.com>
Hi Lambrecht
Many thanks for your report. This is AFAIK first report for ARM9.
There are warnings indeed. Many have been fixed in current CVS. Can you
please report warnings (and possibly propose) fixes in Bugzilla?
Thanks again
Ilija
On 04.04.2012 14:57, Lambrecht Jürgen wrote:
> On 03/18/2012 08:09 PM, Ilija Kocho wrote:
>> Hi Alex
>>
>> Thank you for testing 4.6.2-20120125.
>>
>> 4.6.3-20120315 is our new test release until we upgrade GDB with Jifl's
>> patch:
>> http://ecos.sourceware.org/ml/ecos-discuss/2012-03/msg00064.html
>>
>> Ilija
>>
>>
> Hi all,
>
> I finished building our "Passenger Information System" application with
> gcc 4.6.3 (started with 4.6.2, noticed no difference when switching to
> 4.6.3).
> Before, we used gcc 3.2.1.
>
> I first built ecos v3.0 without any problem.
> Then I built our application, and it took me many days to solve all new
> warnings (we compile with -Werror):
> - unused-but-set-variable -> gave me problems with MISRA rule /16.10/
> (If a function returns error information, then that error information
> shall be tested.) Our PC-lint checker forces any return argument to be
> used, so I had to add __attribute__ ((unused)).
> Also, this warning is annoying for HW drivers: then you sometimes need
> to read some bit just to trigger some behavior, but you are not
> interested in the return value..
> - pointer-sign
> - packed attribute (chars are byte aligned by default, so they are
> "naturally packed
> <http://www.mail-archive.com/lwip-users@nongnu.org/msg02757.html>". So
> don't try to pack chars)
> - '#ifdef ... #elif' cannot be mixed any more ('#ifdef ... #elif
> defined' instead)
> Finally I gave up (for this test) using -Werror because some customer
> code we use is too badly written (I will wait for their update).
>
> But aside from those warnings, it builds fine, and also runs fine on our
> AT91 ARM9 processor.
> No issues so far. Do you know something to watch out for?
>
> Next step is to build the same code version with the old compiler, and
> see with the eCos CPU monitor if there is any difference.
>
> Kind regards,
> Jürgen
>
next prev parent reply other threads:[~2012-04-04 13:18 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 17:01 Gnutools: consideration for upgrade to GCC 4.6 Ilija Kocho
2012-01-13 18:54 ` Bernard Fouché
2012-01-13 19:39 ` Ilija Kocho
2012-01-13 19:09 ` Frank Pagliughi
2012-01-13 19:45 ` Ilija Kocho
2012-01-14 10:22 ` John Dallaway
2012-01-14 16:02 ` Sergei Gavrikov
2012-01-15 17:36 ` Grant Edwards
2012-01-15 18:42 ` Sergei Gavrikov
2012-01-15 21:39 ` Stanislav Meduna
2012-01-23 1:01 ` Jonathan Larmour
2012-01-15 22:21 ` Ilija Kocho
2012-01-15 22:21 ` Ilija Kocho
2012-01-23 1:07 ` Jonathan Larmour
2012-01-16 15:20 ` Grant Edwards
2012-01-16 20:43 ` Sergei Gavrikov
2012-01-16 21:11 ` Sergei Gavrikov
2012-01-17 9:58 ` Bernard Fouché
2012-01-17 10:38 ` Paul Beskeen
2012-01-17 12:28 ` Sergei Gavrikov
2012-01-23 0:59 ` Jonathan Larmour
2012-01-14 16:25 ` Ilija Kocho
2012-01-23 1:13 ` Jonathan Larmour
2012-01-23 18:40 ` Ilija Kocho
2012-01-23 19:29 ` Jonathan Larmour
2012-01-25 12:30 ` Alex Schuilenburg
2012-01-25 20:59 ` Ilija Kocho
2012-01-26 13:36 ` Alex Schuilenburg
2012-01-26 20:18 ` Ilija Kocho
2012-02-13 22:02 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Ilija Kocho
2012-02-20 16:00 ` Alex Schuilenburg
2012-02-20 20:45 ` Ilija Kocho
2012-03-02 16:36 ` Alex Schuilenburg
2012-03-03 13:32 ` Ilija Kocho
2012-03-04 0:10 ` Alex Schuilenburg
2012-03-04 17:49 ` Sergei Gavrikov
2012-03-04 23:08 ` Alex Schuilenburg
2012-03-04 19:37 ` eCos GNU tools 4.6.2-20120125 ready for testing John Dallaway
2012-03-04 23:47 ` Alex Schuilenburg
2012-03-05 8:00 ` Sergei Gavrikov
2012-03-07 13:51 ` Sergei Gavrikov
2012-03-07 11:58 ` Alex Schuilenburg
2012-03-07 13:01 ` Ilija Kocho
2012-03-07 13:39 ` Sergei Gavrikov
2012-03-07 13:13 ` John Dallaway
2012-03-12 16:43 ` Alex Schuilenburg
2012-03-16 15:05 ` Alex Schuilenburg
2012-03-08 17:28 ` Alex Schuilenburg
2012-03-09 9:39 ` Ilija Kocho
2012-03-09 17:15 ` Alex Schuilenburg
2012-03-10 17:16 ` John Dallaway
2012-03-12 16:12 ` Alex Schuilenburg
2012-03-13 13:31 ` Alex Schuilenburg
2012-03-13 14:16 ` Ilija Kocho
2012-03-13 17:47 ` Sergei Gavrikov
2012-03-15 8:50 ` John Dallaway
2012-03-17 14:50 ` Sergei Gavrikov
2012-03-17 20:58 ` John Dallaway
2012-03-17 16:44 ` Stanislav Meduna
2012-03-18 19:10 ` eCos GNU tools 4.6.3-20120315 [Was Re: eCos GNU tools 4.6.2-20120125 ready for testing] Ilija Kocho
2012-04-04 12:57 ` Lambrecht Jürgen
2012-04-04 13:18 ` Ilija Kocho [this message]
2012-05-31 8:42 ` eCos GNU tools 4.6.3-20120315 and link time optimization Bernard Fouché
2012-03-05 8:30 ` eCos GNU tools 4.6.2-20120125 ready for testing Tomas Frydrych
2012-03-05 8:56 ` Tomas Frydrych
2012-03-05 9:50 ` John Dallaway
2012-03-05 9:55 ` Anders Montonen
2012-03-05 14:20 ` John Dallaway
2012-03-05 10:16 ` Ilija Kocho
2012-03-05 12:56 ` Tomas Frydrych
2012-03-03 12:58 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Sergei Gavrikov
2012-01-17 9:37 ` Gnutools: consideration for upgrade to GCC 4.6 Tomas Frydrych
2012-01-17 16:10 ` Stanislav Meduna
2012-01-17 16:25 ` Tomas Frydrych
2012-01-17 16:45 ` Ilija Kocho
2012-01-20 14:42 ` Frank Pagliughi
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=4F7C4A0C.40200@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=J.Lambrecht@TELEVIC.com \
--cc=alexs@ecoscentric.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=jifl@jifvik.org \
--cc=john@dallaway.org.uk \
/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).