rtems - RTEMS Kernel, file-systems, drivers, BSPs, samples, and testsuite.

	Commit message (Collapse)	Author	Age	Files	Lines
*	score: Add RTEMS_CONST	Sebastian Huber	2019-04-09	1	-0/+11
\| \| \| \|	Close #3734.
*	doxygen: Rename Score* groups in RTEMSScore*	Sebastian Huber	2019-04-04	1	-3/+3
\| \| \| \|	Update #3706
*	score: Use __typeof__ for strict ISO C compat	Sebastian Huber	2018-12-06	1	-3/+3
\| \| \| \| \|	Enable the use of RTEMS_DEVOLATILE() and RTEMS_DECONST() in strict ISO C environments.
*	score: Add and use malloc() family attributes	Sebastian Huber	2018-11-12	1	-0/+50
\| \| \| \|	Update #3583.
*	score: Deprecate proc_ptr	Sebastian Huber	2018-11-12	1	-1/+1
\| \| \| \|	Update #3585.
*	small typo	Malte Münch	2018-11-08	1	-1/+1
\|
*	score: Use RTEMS_DEPRECATED for deprecated types	Sebastian Huber	2018-11-08	1	-3/+3
\| \| \| \|	Update #3584.
*	score: Fix legacy RTEMS_STATIC_ASSERT()	Sebastian Huber	2018-10-05	1	-1/+2
\| \| \| \| \| \| \| \| \|	In standard C pointer operands are not allowed in integer constant expressions. Avoid a static assertion based on an array typedef since this could lead to warnings ("variably modified 'x' at file scope" and "typedef 'x' locally defined but not used"); This implementation requires unique messages.
*	score: Remove superfluous semicolon	Sebastian Huber	2018-08-03	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	This avoids warnings like this: warning: ISO C does not allow extra ';' outside of a function [-Wpedantic] RTEMS_DECLARE_GLOBAL_SYMBOL( abc ); ^ Update #3459.
*	score: RTEMS_PREDICT_TRUE(), RTEMS_PREDICT_FALSE()	Sebastian Huber	2018-07-25	1	-0/+28
\| \| \| \| \| \| \|	Add RTEMS_PREDICT_TRUE() and RTEMS_PREDICT_FALSE() for static branch prediction hints. Close #3475.
*	score: Macros to declare and define global symbols	Sebastian Huber	2018-06-21	1	-1/+33
\| \| \| \| \| \|	Add RTEMS_DEFINE_GLOBAL_SYMBOL() and add RTEMS_DECLARE_GLOBAL_SYMBOL(). Update #3459.
*	Remove make preinstall	Chris Johns	2018-01-25	1	-0/+415
	A speciality of the RTEMS build system was the make preinstall step. It copied header files from arbitrary locations into the build tree. The header files were included via the -Bsome/build/tree/path GCC command line option. This has at least seven problems: * The make preinstall step itself needs time and disk space. * Errors in header files show up in the build tree copy. This makes it hard for editors to open the right file to fix the error. * There is no clear relationship between source and build tree header files. This makes an audit of the build process difficult. * The visibility of all header files in the build tree makes it difficult to enforce API barriers. For example it is discouraged to use BSP-specifics in the cpukit. * An introduction of a new build system is difficult. * Include paths specified by the -B option are system headers. This may suppress warnings. * The parallel build had sporadic failures on some hosts. This patch removes the make preinstall step. All installed header files are moved to dedicated include directories in the source tree. Let @RTEMS_CPU@ be the target architecture, e.g. arm, powerpc, sparc, etc. Let @RTEMS_BSP_FAMILIY@ be a BSP family base directory, e.g. erc32, imx, qoriq, etc. The new cpukit include directories are: * cpukit/include * cpukit/score/cpu/@RTEMS_CPU@/include * cpukit/libnetworking The new BSP include directories are: * bsps/include * bsps/@RTEMS_CPU@/include * bsps/@RTEMS_CPU@/@RTEMS_BSP_FAMILIY@/include There are build tree include directories for generated files. The include directory order favours the most general header file, e.g. it is not possible to override general header files via the include path order. The "bootstrap -p" option was removed. The new "bootstrap -H" option should be used to regenerate the "headers.am" files. Update #3254.