From: Ingo Blank on 5 Dec 2005 13:48
since the release of HP-GCC 2.0 is just a few days away, I'm posting a
preliminary README, since there was some uncertainty in the past, in
particular in context with the Windows distribution.
* HP-GCC version 2.0 *
The release of the 2.0 version focuses mainly on significant
enhancements to the technological infrastructure of the libraries
and the ARM toolbox.
This includes the default generation of Thumb instructions, which reduces
executable code size by 20-30 percent on average.
Furthermore HP-GCC 2.0 introduces the so called "VC" (= virtual code)
allows for code in virtual memory. This finally moves the runtime system
again closer towards
full standard C compliance, since it's now possible to assign static
(compile time) pointers to
code locations (function pointers).
The change from "MMU" to "VC" technology introduces the up/backward
incompatibility for binaries.
That is, it's not possible to execute 1.x binaries with the new Toolbox as
it is not possible to
execute 2.0 binaries with the old Toolbox as well.
The team took all technical possible precautions to prevent the user from
Despite this, please take care for yourself and avoid version mix under all
There is a also a new library "decNumber", which implements arbitrary
precision BCD arithmetics.
This high performance lib was donated by IBM Corporation to the Free
The HP-GCC team managed to port it to the HP49G+ calculator.
This is work in progress, since it's not yet fully integrated into the math
But it's already included for the technically interested user and a field
In this context please note, that the binary exception of the HP-GCC license
does not apply,
if parts of this library are linked to an executable or parts of the library
sources are integrated
into user code.
All usage of the "decNumber" library binds the user to the pure GPL, without
The Windows distributions now comes per default with a graphical UI and a
basic IDE (Programmers Notepad).
The support for the "small" models 39G and 48II was discontinued.
The reason for this is twofold.
On one side there was very low resonance and feedback compared to the
maintenance effort and on the other are the future plans for HP-GCC
contradicting "low resource" devices, especially without mass storage.
The usage of HP-GCC implies, that you have read this document and agree with
it's content, in particular
with the license terms.
December 5th, 2005
The HP-GCC Development Team
From: Arnaud Amiel on 5 Dec 2005 15:04
"Ingo Blank" <ingo.news01REMOVE_UPPERCASE(a)hpgcc.org> wrote in message
> This includes the default generation of Thumb instructions, which reduces
> executable code size by 20-30 percent on average.
Good, that was one of my main concern with hpgcc. I still believe that
adding a BZ option to the ARM toolbox would be a good idea but I have to
check the new hpgcc first.
Thanks for all the work that has been done and hopefully will be.
From: Brother-Peter on 5 Dec 2005 15:17
"Arnaud Amiel" <aamiel(a)hotmail.com> wrote in message
> "Ingo Blank" <ingo.news01REMOVE_UPPERCASE(a)hpgcc.org> wrote in message
>> This includes the default generation of Thumb instructions, which reduces
>> executable code size by 20-30 percent on average.
> Good, that was one of my main concern with hpgcc. I still believe that
> adding a BZ option to the ARM toolbox would be a good idea but I have to
> check the new hpgcc first.
> Thanks for all the work that has been done and hopefully will be.
My next major project will be learning C (again)
1st I'll wait & C
if HPQ can come up with a new
hp 49g++, 48gIII, 39g++
From: Steen Schmidt on 5 Dec 2005 17:37
Ingo Blank wrote:
Suberb, Ingo (and the rest of the team)! I'm really tempted to take a
look at it - probably will :-)
From: xEaGLe on 5 Dec 2005 19:16
Good news! very good ones indeed.
Thank you, guys for the effort that u made in 2005. I hope we can see
new features in C for the 49g+ in 2006.
thx a lot