v00x vs v003 firmware size difference

[prplz]

For example:
V002 = 6816 B
v003 = 6756 B

I believe most of it is caused by v003 using libgcc.a from the repo and v00x using it from the system.
Relevant line in ch32fun.mk is LDFLAGS+=-L$(CH32FUN)/../misc -lgcc in the v003 block. I haven't tested adding it to v00x yet.

[TommyMurphyTM1234]

I believe most of it is caused by v003 using libgcc.a from the repo and v00x using it from the system.

The likes of the map and list files should clarify exactly where each byte of each linked image is coming from and eliminate any speculation.

[prplz]

ok i tried making it link against the libgcc.a in the repo and the binaries match except an extra instruction needed to setup the stack pointer due to bigger sram.

[cnlohr]

Should this be closed?

[prplz]

No, I think you need to add LDFLAGS+=-L$(CH32FUN)/../misc -lgcc to the v00x block, assuming you think it’s right to use the vendored one for v00x (I don’t know the consequences of that)

[cnlohr]

I think we want to only force that for the v003. We could consider getting other platform-specific ones, but it would theoretically be less efficient or worse to use the v003 one on any of the others, since the others have a multiply instruction.