public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: Alex Schuilenburg <alexs@ecoscentric.com>,
	ecos-devel@ecos.sourceware.org,
	    John Dallaway <john@dallaway.org.uk>
Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing
Date: Tue, 13 Mar 2012 17:47:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1203132000500.8871@vostro> (raw)
In-Reply-To: <4F5F5691.4090009@siva.com.mk>

On Tue, 13 Mar 2012, Ilija Kocho wrote:

> Hi Alex
> 
> Thank you for the update.
> 
> On 13.03.2012 14:30, Alex Schuilenburg wrote:
> 
> [snip]
> >
> > Is it worthwhile continuing testing 4.6.2 given
> > http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001468 ?
> 
> It would be good for us to decide what to do ASAP at latest till end of
> this week.
> 
> I am testing 4.6.3 on hardware FPU - Cortex-M4F and that bug seems fixed.
> 
> I would  also like to check this one reported by Sergei
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001468#c25 only I don't
> have ARM7TDMI handy. It would be nice if somebody can do this test: Try
> 4.6.3 on cases that with 4.6.2 pass ARM but fail Thumb?

That talk was about (this bug was fixed in 4.6.3)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49641

I was able to reproduce #49641 in 4.6.2 with

  cdl_option CYGHWR_THUMB {
      user_value 1
  };

  /tmp/cceuQCd7.s: Assembler messages:
  /tmp/cceuQCd7.s:834: Warning: value stored for r3 is UNKNOWN

disassemble output with objdump:

  /tmp/t/net/bsd_tcpip/current/src/sys/netinet/net_bsd_tcpip_ip_icmp.o:
     6:    c30c          stmia    r3!, {r2, r3}

*BUT*, IMHO, this is not issue for this report:
> Ref: http://sourceware.org/ml/ecos-devel/2012-03/msg00024.html

I tried to build and run "thumb" tests for NXP ARM7TDMI (LPC2294) using
corresponding RedBoot/GDB

  ecos-v3_0-branchpoint GCC 4.3.2  most of tests failed
  ecos AnonCVS          GCC 4.3.2  most of tests failed
  ecos AnonCVS          GCC 4.6.2  most of tests failed
  ecos AnonCVS          GCC 4.6.3  most of tests failed
 
Thus, it looks like that GCC 4.6.2 is not point of those fails.

BTW, I never tried ro run "thumb" blobs before on my target and maybe
I should turn on/off more CDL options than just to force CYGHWR_THUMB
option.

So, I agree with the said "Thumb support looks broken" at the least for
lpc2xxx, lpc24xx variants, but, it seems to me it was broken even before
eCos 3.0.

Sergei

> In meantime, Alex, I think you can suspend testing with 4.6.2, but
> please keep the results.
> 
> Thank you again
> 
> Ilija
> 

  reply	other threads:[~2012-03-13 17:47 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 [this message]
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
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=alpine.DEB.2.00.1203132000500.8871@vostro \
    --to=sergei.gavrikov@gmail.com \
    --cc=alexs@ecoscentric.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    --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).