[En-Nut-Discussion] Use of alloca in Nut/OS

Henrik Maier hmlists at focus-sw.com
Tue Aug 12 02:37:25 CEST 2008


I also suggest to create a set of reference platforms and toolchains.
Maybe a set of 5 or 6 with defined compiler versions and a selection of

Before committing code to CVS, a developer can compile against these
reference platforms/toolchains to verify compliance. This could be done in
an automated way by a master makefile.

That way we know that a change in the code base which benefits one platform
does not break compilation on another platform or with an older version of a


> -----Original Message-----
> From: en-nut-discussion-bounces at egnite.de [mailto:en-nut-discussion-
> bounces at egnite.de] On Behalf Of Harald Kipp
> Sent: Monday, 11 August 2008 7:04 PM
> To: Ethernut User Chat (English)
> Subject: Re: [En-Nut-Discussion] Use of alloca in Nut/OS
> In certain situations defaults may be provided based on the platform or
> the toolchain in use. In general, however, the code should be based on
> the least common denominator. In our special case, the libraries should
> be compilable without runtime routines like strtok_r or alloca, which
> are not used elsewhere in the code base. This has two advantages:
> Porting code to new compilers and targets becomes easier and in case of
> problems with advanced runtime library implementations we are able to
> switch back to the simple, possibly less efficient code.
> Harald
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion

More information about the En-Nut-Discussion mailing list