Re: GNUPro Development, v850



In message <m31vwo43ma.fsf@xxxxxxxxxxxxx>, Rich Walker <rw@xxxxxxxxxxxxxxx> writes
Chris H <chris@xxxxxxxxxxxx> writes:

BTW can you still get the original GCC (before they changed cores)?

Local GCC mirror:
http://gcc-uk.internet.bs/releases/

GCC source repository, so you can tell why a change was made and when:
http://gcc.gnu.org/viewcvs/

However most GCC don't use that as you say below

Availability of GCC packages from my distributor (Debian) for various architectures:
http://packages.debian.org/search?keywords=gcc

Most people use a gcc from one of the distributors who do their own patches and modifications and in the case of a lot of them include proprietary IP in the package. Not all the stuff the distis do is fed back.

You have a Debian-GCC not a "gcc" compiler.

Search all bugs reported to Debian for GCC-related packages:

But NOT for "GCC" only Debian's GCC and there a re a lot of other similar but different GCC distributions. Red had pointed out the performance in theirs varies from version to version and is NOT the same as any FSF version.

Saying "GCC" is like saying A compiler family where no two are likely to be the same. In a discussion yesterday with a FOSS devotee he said ONLY the FSF GCC are legitimate to call GCC the rest are deviations. Nice to know there is consistency.

Behaviour and efficiency varies wildly, even for the same target and version number. One company had 4 programmers using GCC... turned out they are using three different compilers even though they were for the same targets and had the same version number.

Some one yesterday said IAR made one error (in his opinion). That is enough... I will never use them again. Compared to the state of the GCC market IAR are positively saintly.

What was your big value-add again?

We deal mainly in critical systems.
We can validate the compilers.

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/



.



Relevant Pages

  • Re: Whats the story with the "end of XP"?
    ... Support gives them access to the larger body ... The same compiler suite may be "best" in both ... In the case of ByteCraft compilers, you are truly expert in your field, you work closely and rapidly with customers if there are any issues, and you have top class testing and quality control. ... understanding the inner workings of a relatively simple compiler like GCC ...
    (comp.arch.embedded)
  • Re: 10.0-CUR r226986 && ports (general)
    ... configure:3232: checking for gcc ... Configured with: FreeBSD/amd64 system compiler ... configure:5483: checking how to associate runtime and link libraries ... configure: failed program was: ...
    (freebsd-current)
  • [RFC][PATCH-2.6] Clean up and merge compiler-*.h
    ... the kernel headers in include/linux to include/linux-abi. ... * Common definitions for all gcc versions go here. ... -/* Some compiler specific definitions are overwritten here ...
    (Linux-Kernel)
  • Re: LPC900/80C51 Compiler Toolchain
    ... >> supported by GCC, and so they invest. ... > if they already have their in-house compiler. ... one of the main companies in the Symbian consortium ... vendor to provide a good compiler for Atmel AVRs and eventually became ...
    (comp.arch.embedded)
  • Re: Looking to buy a used embedded cross compiler
    ... I have this home project and am currently set up with a MS Windows gcc ... cross compiler to 68000. ... If you are looking for a good compiler for the m68k, and don't want to spend very large sums of money, then gcc is almost certainly your best choice (personally, I think gcc is the best choice for the 68k target even if you /do/ have lots of money to spend, but not everyone agrees on that). ... On the m68k, the standard calling convention IIRC is to use D0 and D1 for the first two arguments, then to push the other arguments on the stack. ...
    (comp.arch.embedded)