Re: [MiNT] C99 stuff in public GEMlib headers?

[Arnaud BERCEGEAY <arnaud.bercegeay@free.fr>]

Hello,

2012/11/15 Eero Tamminen <oak@helsinkinet.fi>

Could GEMlib public headers also be made ANSI-C compliant?

Currently headers have one inline for appl_init() which is
typically called only once in program life-time, so it's not
performance critical.

It's a bit annoying if a header forces all SW including it
to be compiled  with -c99/-std=c99.  And e.g. AHCC doesn't
even support "inline".

The file compiler.h is here for compatibilty issues of the compiler (it does the job for gcc, old version of gcc, pure C, sozobonx C, and maybe lattice C too...)

For performance question, i don't think the extra function call (mt_aes -> non-mt_aes) is significant.

BTW, when mt_aes has been integrated into gemlib (this was the begining of MGEMLIB, a fork of gemlib), some work has been done to optimize AES calls, and IIRC, the result was that MGEMLIB was faster than legacy gemlib.

I think current version of gemlib is even faster thanks to ASM optimisation of AES trap done since then.

Arnaud.