Atari-Forum

LS There is a new version available on my home page Changes: January 17 2017 v5.5 Compiler: Commandline versions: Do not wait for a keypress under MiNT or MagiC. All: Wrong code was generated for comparison to a constant in rare situations, resulting in a tst to a immediate. Now either a branch or n...

LS There is a new version available on my home page: http://members.chello.nl/h.robbers/ Changes: June 6 2016 v5.4 Compiler: Fixed a bug in register health analysis where in certain rare circumstances too many operations were discarded. Shell: (not AHCCST) New menu item: Project-->PRJ from folder. P...

They are just unharmful messages that I forgot to remove from the final version
of the compiler when creating the ColdFire version and can be ignored.

mov3q is a ColdFire special move instruction. It moves a small constant. (3 bits)

Sorry, my mistake.
Do you still have your old ahcccf.cfg ?

Sinclude is for compiling AHCC itself, whether by itself or by Pure C.
Its purpose is to define ALL int as short. (less confusion). It might also have definitions only relevant to the AHCC suit of programs.

I'll sync sinclude and include regarding general available definitions.

Sorry for being late. I suppose you all read comp.sys.atari.programmer ? January 21 2016 v5.3 Compiler: Fixed a bug that prevented proper casting of constants by explicit casting. Fixed wrong code for casting the result of a comparison to a float (e.g. R1 = R2 < R3 where all R's are floats). Fixed a...

august 23 2015 v5.2 Shell: Compare folders: Mismatch display order of filenames reversed. Double clicking 'Mismatch': first file is left on top. Compare files: (^2) flipflop between red and green according to equality of selected lines. (red: unequal, green : equal). Compiler: Small code improvement...

In some cases your implementation of standard libraries is much more efficient that the one provided with Pure C. So if we need floating point is it possible to use Pure C compiler but link with AHCC libraries? Please study math.h. All incarnations of AHCC implement overloading of existing operator...

I believed that the goal was just to replace Pure C with a maintained compiler. That was indeed my intention. Alas, I was too lazy to replace the (rather big) Pure C floating point library. So I took the easiest way: 68020+ fp by FPU, 68000 No fp at all. Long ago I asked in a news group (c.s.a.prog...

When creating AHCCST I wanted to be as secure and rogorous as possible. So I removed anything that even smelled like floating point.

Remember that AHCCST was created for reducing memory usage for ST users not needing floating point.

Henk.

A new version is available at http://members.chello.nl/h.robbers/ Changes: september 18 2014. v5.1 Shell: KIT::match options: 4 radio buttons word, any, prefix, postfix The latter very useful for finding usage of struct/union members e.g. ->large, not ->larger A few better names in the big window st...

LS There is a new version available on my Home page http://members.chello.nl/h.robbers Changes: january 10 2014 v5 general: Back to small version number. (Greetings mister Thorvalds Replaced 'string' back to char * for single declarators, to Wstr for declarator lists. (appeared to be a little confus...

AHCC does not "inline" assembly the way GCC does. In stead you can write assembler functions as part of a C file and its infrastructure. #include "whatever.h" int save_i; void __asm__ asm_func(int i) { move d0, save_i ; do your asm things using names from whatever.h rts } void C_function(void) { ......

I am afraid that AHCC's memcpy is a very opportunistically written C routine (just a simple char loop).
Written with the aim to be correct with little effort.
This has nothing to do with inherent qualities of compiled or interpreted code.

Feel free to produce better performing versions.

Ahh I understand. So the startup code is normally linked first to ensure it is run at start and then handles everything to turn over the control to the other modules. LD: input files will appear in the output file (when something in them is referred to) in the same order as in the project file. So ...

For AHCC all I need to know is for the .PRJ file. Do i simply state my own startup file (as a tweaked .c file) first or do I have to compile the startup seperately andf then link the .o file as with the default startup code? There is nothing special. Any file appearing in the prj as first will be c...

Basically I want to move these into a different startup file so it is transparent and I don't have to call it from main or any other function anymore. Then all I have to change is my .PRJ file to use the new startup and the other code can concentrate on the things I want to code. Your approach is c...

Hi

FYI: AHCC (which supports 68881/2) runs only on Atari's that have such a coprocessor via line_A
AHCCST only runs on 68000 and does NOT support floating point.
Reason: I did not write a software floating point package.

Henk Robbers.

I noticed the default startup code for AHCC is provided as a .C file in the source package. I have a few customizing questions (and want to share them publically). I was wondering if it was possible to integrate my setup codes into a reusable startup package to reduce overhead of rewriting init cod...

LS There is a new version availble on: http://members.chello.nl/h.robbers/ october 3 2012 v4.14 General: Removed leftover traces of a debug session some time ago. Compiler: Fixed a bug where a static string was not properly used (changed without copying) The bug resulted in incorrect compiling of ah...

LS
There is a new vwersion available on
http://members.chello.nl/h.robbers/

Only 1 change:

september 28 2012
v4.13
Compiler(Coldfire target)
Fixed a regression in 4.12 concerning use of 'mov3q' instruction.

LS A new version available on: http://members.chello.nl/h.robbers/ Changes: september 22 2012 v4.12 General: Changed 'xref' to 'pdb' in all source files (pdb = Project Data Base, xref.... is only part of it). Compiler (Coldfire target): Fixed non Coldfire code for 'move' in some cases. Also fixed ca...

FYI:

AHCC and Pure C implement full K&R 2nd edition (ANSI C or C89)

Megamax C is K&R 1st edition.

PS:

Parameters passed to C functions in D0,D1,D2, A0 or A1 are not preserved after the call.

D0,D1,D2, A0,A1 are scratch registers in C functions and are supposed to be destroyed. All other registers are saved and restored if used by C functions. When you call a assembler function from C, you must do the same in the asm function. ie: save and restore registers > D2 or > A1 if used by the fu...