Finding BSP specific information (preferably via Makefile variables)

Gedare Bloom gedare at
Tue Jun 8 19:36:29 UTC 2010

I'll take a stab at this, though a caveat that I am also a student so
don't take my word for it :)

Most of the information you're looking at is actually CPU Model Family
dependent, so it may live in cpukit/score/cpu or be part of the newlib
/ libc header files. Unfortunately, I'm not sure how any of this might
be exposed in the configuration.

cpukit/score/cpu/CPU_MODEL/rtems/score/cpu.h contains some definitions
that cover this, and you can find documentation in the CPU Supplement
in the RTEMS documentation (
).  This will, for example, show you the processor endianness via
either the CPU_BIG_ENDIAN or CPU_LITTLE_ENDIAN cpp defines.

Some of the other things you are wondering about are defined in some
types.h, stdint.h, or some limits.h file, which I think will be
something out of libc.  Since these are standard, there is probably
some way that configure tools query the target libc to determine these
values, so I think that would be what you want to do.

Hope that helps,

On Tue, Jun 8, 2010 at 3:05 PM, Bob Kuo <bobjkuo at> wrote:
> Hello all
> For my Google Summer of Code project I am porting the Parrot Virtual
> Machine to RTEMS.  To configure and build Parrot I need to know some
> BSP specific information.  For example, I need to find:
> if we use 'short' or 'int'
> what type should hold our floats
> min and max 'int' value
> min and max 'float' value
> int and pointer sizes
> big or litte endian
> I imagine these values vary by BSP.  Is this kind of configuration
> information available, perhaps through the BSP-specific Makefile?
> Thanks,
> b
> _______________________________________________
> rtems-users mailing list
> rtems-users at

More information about the users mailing list