From gcc to vbcc.

[Cowcat]

Working on some big/old classic source code:

To the fellow coders: What are the key factors or things to look after to arrange gcc source to be compatible enough to work with vbcc? (I'm using posix lib from vbcc by the way)

[phx]

If you work with gcc and want to keep it compatible with other compilers (like vbcc), use at least -std=c99, -ansi and -pedantic options to avoid gcc-specific extensions and keep the code clean.

If you work with vbcc and try to port a gcc source you will likely see the problems very soon.

If you have the time, try to remove all Posix stuff which has to be emulated. The gcc-version should compile with -noixemul and the vbcc-version shouldn't require PosixLib. A real Amiga program is always cleaner.

[Cowcat]

First is the makefile nightmare

I don't have nowadays any complete gcc stuff vbcc to me "is" the way to go.

Problems in the code are related to some calls to things like bzero, or fopen ,etc. So posix helps: No idea of how to implement all that (now).

Some of the object files need to be compiled with amitcp includes as something doesn't work with posix includes all the way to the different binaries (dlls)

I hacked my way to produce a binary: Of course it doesn't work but at least I does some output.

Complicated stuff

[kamelito]

@PHX
a bit off topic but is VBCC better performance wise than GCC? Any comparison with newer version of GCC?

http://sun.hasenbraten.de/vbcc/index...iew=benchmarks

Kamelito

[phx]

Originally Posted by Cowcat

I don't have nowadays any complete gcc stuff vbcc to me "is" the way to go.

If we could only find the time to stabilize the current development for the next release. There is always a bug left to fix...

Problems in the code are related to some calls to things like bzero, or fopen ,etc.

#define bzero(p,l) memset(p,0,l)

fopen is standard ANSI-C. Perhaps you're refering to Posix-open()? Use dos.library Open() instead, for unbuffered I/O.

So posix helps: No idea of how to implement all that (now).

Any Unix system helps, where you can read about all those functions in the man pages.

[phx]

Originally Posted by kamelito

a bit off topic but is VBCC better performance wise than GCC?

Maybe still in some cases. Also depends on the CPU backend used.

Any comparison with newer version of GCC?

I didn't make any comparison since many years. GCC has certainly improved with version 3 and 4. But it also became quite bloated. And the 68k backend starts to "bit-rot".

[Cowcat]

@phx
Located bzero Thanks! Maybe also "strdup" can be defined easily.

But others like stat, putenv, isort, mkdir .... maybe I will have to do an special "posix.o" with all in it.

[Cowcat]

Can't figure out this:

#define	CRAP(x) (int)&(((something_t *)0)->x)

field_t fields[] = {
	{"whatever", CRAP(whatever),MORE},
};

gives me "initializer not a constant". Seems to work for gcc....

[thomas]

#include <stddef.h>

#define CRAP(x) (int)offsetof(something_t,x)

[Cowcat]

Originally Posted by thomas

#include <stddef.h>

#define CRAP(x) (int)offsetof(something_t,x)

Awesome Thanks !

But now I have to figure out something like (anotherthing.other, x) ....seems like I need a ")" and a "}" expected. Just tried fast your recipe

EDIT: Sorry for (whatever.whatever)