HP-GCC 2.0 to be released soon
in [HP48]
|
Prev: HP 40GS
Next: Card for the HP49G+
From: manjo on 5 Dec 2005 19:45 Hello Ingo, hello HPGCC, I'm not sure if i asked this before, here's to be sure : is there an effective way to embed custom ASM code in to the C ? some c code here arm (or thumb) { loop: some asm code here bne loop } continues with c code -this would be great, i understand it's up to compiler, if there are other ways, please let me know, i'm sure people would be interested. manjo
From: Ingo Blank on 5 Dec 2005 20:29 manjo wrote: > Hello Ingo, hello HPGCC, > > I'm not sure if i asked this before, here's to be sure : > is there an effective way to embed custom ASM code in to the C ? > yes, you can embed arbitrary inline assembler statements, Refer to the gcc manual for details. Be aware that modern compilers generate fairly good code and that hand optimizing assembler on RISC processors is not an easy task. What I mean is, it's probably not worth the effort... Also makes it your code processor dependent (=> hard to port). Let alone maintenance. In the early days of HP-GCC we (in particular I) had written lots of code in assembler, but we finally ported all to C with the exception of some very specialized parts in certain low level routines (cache flush in the loader etc.) hth Ingo
From: Lilian Pigallio on 6 Dec 2005 05:17
Great :) "Ingo Blank" <ingo.news01REMOVE_UPPERCASE(a)hpgcc.org> a ?crit dans le message de news:43948b6b_2(a)news.arcor-ip.de... > > Hello, > > 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. > > <README> > > ********************** > * 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 > the > executable code size by 20-30 percent on average. > > Furthermore HP-GCC 2.0 introduces the so called "VC" (= virtual code) > technology, which > 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 > damage. > Despite this, please take care for yourself and avoid version mix under all > circumstances. > > 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 > Software Foundation. > 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 > framework. > But it's already included for the technically interested user and a field > for experimentation. > > 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 > exception. > . > 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 > > </README> > > Regards > ibl > > > > |