Public kudos to Frank and Volker for their work on vbcc, particularly to Frank for his help and patience with my often naive questions.

sizeof macro, or mabye it's offsetof or both, can't remember, still doesn't support nested structs.

Anyway, excellent stuff of course, big thanks to the author.

The built-in __offsetof attribute doesn't appear to, but you could always fall back on a traditional offsetof macro.

Can you use sizeof on struct members in any C implementation? I do sizeof(((struct s *)(0))->nested.mem).

Is this version already included in the Amiga OS 4.1 public SDK or not ? Thanks :-)

@Trev
That "traditional" macro approach doesn't work with VBCC, it just refuses to cast 0 and output an error, can't remember which...

@Jose

I suppose it wouldn't work if you put a 0x10000000 in place of 0, for example, then subtracted it off later?

@Jose

It worked for me when I posted it:

C:\vbcc>type nested.c
struct s {
struct {
int mem;
} nested;
};

main()
{
int memsize = sizeof(((struct s *)(0))->nested.mem);
}

C:\vbcc>vc -v -k nested.c
vc frontend for vbcc (c) in 1995-2008 by Volker Barthelmann
vbccm68k -quiet "nested.c" -o= "nested.asm" -O=1 -IC:\vbcc\targets\m68k-amigaos
\include -IC:\vbcc\NDK_3.9\Include\include_h
vasmm68k_mot -quiet -Fhunk -phxass -opt-pea -opt-clr -opt-fconst "nested.asm" -o
"nested.o"
vlink -bamigahunk -x -Bstatic -Cvbcc -nostdlib -LC:\vbcc\targets\m68k-amigaos\li
b C:\vbcc\targets\m68k-amigaos\lib\startup.o "nested.o" -s -Rshort -lvc -o a.o
ut

C:\vbcc>type nested.asm
idnt "nested.c"
opt 0
opt NQLPSMR
section "CODE",code
public _main
cnop 0,4
_main
movem.l l2,-(a7)
moveq #4,d0
l1
l2 reg
l4 equ 0
rts
; stacksize=0

EDITS: Formatting...

@nube78

No, the version included in the Amiga OS 4.1 public SDK is version 0.8i but it is very easy to update to the latest version.

The new OS4 SDK maintainer said he doesn't care for vbcc.

And right, __offsetof() for a member of a nested struct still doesn't work. But I didn't even know about it, when nobody reports it. Too late for 0.9a. ;)

@phx

Good to see you here, Frank.

phx wrote...

That's narrow minded. Having more options is always better. So many people want to have the best when what is best usually is not the best for everything. Don't be discouraged. Just make vbcc better ;-). Vbcc is already better than gcc in most ways on AmigaOS 68k if you ask me. Have you seen the code that gcc generates? You can't beat the Amiga support for vbcc either :-P.


Yes we all need to start communicating better. Bug reports are vital to development.

Is vbcc 0.9a available somewhere yet?

@phx


I would have reported it if I'd run into it but I don't use offsetof that much.

Who's the new SDK maintainer anyway? Or is that still supposed to be a secret?

Not yet. It is finished since months. A last beta-testing bug was fixed four weeks ago, but I still didn't find the time to run all test suites. 0.9a will include many important bug fixes, especially for 68k.

I do not accuse a person in public, although he is the reason I gave up my OS4 developer status a few weeks ago.

@salass00
There isn't one. The SDK is prepared by whomever happens to get the job that release.

@phx
Wouldn't it have been better to try and resolve the matter privately before taking such drastic action?