[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-gcc-list] avr-gcc credibility

From: J.C. Wren
Subject: RE: [avr-gcc-list] avr-gcc credibility
Date: Thu, 1 Aug 2002 12:38:12 -0400

    This brings up an interesting point.  ICC has the code compressor, which can do some very effective compression (I've seen as much as 20%) on the final binary (this is not gzip type compression, but analyzing the code for repeated code blocks, etc).  I'm surprised this hasn't been adopted by the GCC micro controller community.  GCC does a decent job of optimization on a per-module basis, but has no facility to do dead code removal, nor common code compression. 
    There is a slight speed penalty for the compression, since it makes subroutines out much common code, but not all microcontroller jobs are time critical.  Something like a LCD user interface, the delay is unnoticable.
-----Original Message-----
From: address@hidden [mailto:address@hiddenOn Behalf Of E. Weddington
Sent: Thursday, August 01, 2002 11:41
To: address@hidden
Subject: Re: [avr-gcc-list] avr-gcc credibility

Concerning bugginess (lack thereof) and upgrade temptation:
I'm currently writing software for a wireless RFID probe and base station receiver for the laboratory market. The probe and base both use an ATmega128. Both sets of software (probe and base combined) are currently over 15,000 lines of code and I'm not even done yet. Before this project I was using the IAR compiler for the Atmel AVR on othe projects. Due to cost considerations in "upgrading" their product to use the ATmega128 I decided to finally check out GCC. At the time, they were just starting to integrate support for that product. I downloaded the avrgcc128 beta 2 version and I've been using it ever since without any problems whatsoever. I'm not upgrading the compiler during this version unless I have to. I probably will upgrade in between versions of this product, but I don't expect any real issues to come up. The support via the list has been great, and you really get timely information about any problems with the compiler / library, which may or may not affect you. The only down side (and its a small down side) is that documentation is not exactly "centralized". If you want an answer, you can find it in some documentation somewhere; you just have to be willing to search around and follow different links to find it, but it can be done.
-------Original Message-------
Date: Wednesday, July 31, 2002 11:57:11 PM
Subject: Re: [avr-gcc-list] avr-gcc credibility
The trap with gcc (and avrgccc) is that it's tempting to upgrade every time
there is a new patch. Don't do that unless there is a compelling reason to.
New patches introduce new bugs and new behaviors.

Test the compiler, examine it's output and build up your confidence this
way. So far on this forum there have been very few real bug reports. That's


  IncrediMail - Email has finally evolved - Click Here

reply via email to

[Prev in Thread] Current Thread [Next in Thread]