Re: Which GCC Version to use with ARM7 ?

Rasmus Fink <i.hate.spammming@xxxxx> writes:


For a new product we are going to use an ARM7 and are now going to make
an important choice : Should we stay with IAR or should we use GCC. We
are current leaning a bit towards GCC but we need som extra input here :

What version should we use ?

3.x.x is not the newest but I beleive many of its bugs are known.
4.1.0 is the newest and generally considered stable.

What are your experiences regarding code density, bugs and snags on the
different versions of GCC ?

I don't think I have ever found a bug with gcc-arm. No problems with
the compiler, it is excellent. I have been using the GNUARM
distribution which comes with "Newlib". What device (ram and rom size)
are you targetting? This may affect your library choice. Newlib is
very powerful but needs care, and avoidance/replacement of some areas,
if using with smaller devices.

Rowley Associates <> package gcc with their
own debugger and libraries, this may be an option for you. Not used
them but looks good. They sell low cost debugging hardware too it
would appear.


John Devereux

Relevant Pages

  • not able to install source navigator 5.1.14 on suse 10.2
    ... Configuring for a i686-pc-linux-gnu host. ... checking for gcc... ... checking whether struct tm is in sys/time.h or time.h... ... checking for Solaris2.4/Tru64 strtod bugs... ...
  • Re: [PATCH] kbuild: Disallow GCC 4.1.0 / 4.1.1
    ... other bugs anyway, so it's probably a good idea. ... ...or we can just merge Adrian's patch from June 2008 which also fixes ... Subject: kbuild: Disallow GCC 4.1.0 / 4.1.1 ... Sorry, your compiler is too old, too buggy or not recognized. ...
  • Re: need help on CFLAGS in /etc/make.conf please
    ... The delay in my response here was due to pest control in our building ... I do not want to override the original's optimization settings either ... taken together with the GCC 3.x Known Bugs ...
  • Re: Small, understandable Forth
    ... I know bugs in PFE, in FICL, in pForth, but not in GCC, ... than a niche language like Gforth. ... "marker smth ... ...
  • Re: [PATCH][Regression] x86, 32-bit: trim memory not covered by wb mtrrs - FIX
    ... highest_pfn and end_pfn is unsigned long aka 32 bit ...could overflow. ... i think the 64-bit behavior of gcc is inherently dangerous, ... numerous subtle bugs in that area. ... So if there's no helpful gcc warning that already exists, ...