This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

_ELIX_LEVEL problems


What is supposed to happen when _ELIX_LEVEL is not defined?
We used to build newlib as for maximum EL/IX level.  Now we
only build files in EL/IX level 0, but these are build for maximum
EL/IX level.
Is _ELIX_LEVEL supposed to be always defined now?  But if so, there
is no point of having lots of
#if !defined (_ELIX_LEVEL) || _ELIX_LEVEL >= 2
(and even some #ifndef _ELIX_LEVEL || _ELIX_LEVEL >= 2)
in the sources.
Moreover, vfscanf.c uses iswspace and other wide character functions
without regard to the elix level.
Obviously there need to be some guard there, but simply copying one
of the existing ones won't help because of the above problem - since
_ELIX_LEVEL is not defined for embedded platforms (at least not
for sh-elf), the  offending code would still be included.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]