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

	Commit message (Collapse)	Author	Age	Files	Lines
*	rtems: Add files to Doxygen groups	Sebastian Huber	2023-07-26	1	-10/+40
\| \| \| \| \| \| \|	Provide basic Doxygen comments. Update #3706. Update #3707.
*	Update company name	Sebastian Huber	2023-05-20	1	-1/+1
\| \| \| \| \|	The embedded brains GmbH & Co. KG is the legal successor of embedded brains GmbH.
*	Do not use RTEMS_INLINE_ROUTINE	Sebastian Huber	2022-09-19	1	-1/+1
\| \| \| \| \| \| \|	Directly use "static inline" which is available in C99 and later. This brings the RTEMS implementation closer to standard C. Close #3935.
*	Revert "linkersets.h: Fix gcc 12 warning"	Sebastian Huber	2022-08-29	1	-1/+1
\| \| \| \| \| \|	This reverts commit f930206724e65f188fe3b095826ceb1b11000f65. The linker set begin must be a symbol and not a zero-initialized item.
*	linkersets.h: Fix gcc 12 warning	Ryan Long	2022-08-19	1	-1/+1
\| \| \| \| \| \| \|	Changing the offset from 0 to 1 got rid of a warning stating that offset 0 is out of bounds. Updates #4662
*	cpukit/include/rtems: Change license to BSD-2	Joel Sherrill	2022-03-25	1	-3/+22
\| \| \| \|	Updates #3053.
*	cpukit/: Scripted embedded brains header file clean up	Joel Sherrill	2022-03-10	1	-6/+0
\| \| \| \|	Updates #4625.
*	cpukit: Explicitly enforce alignment requirements	Kinsey Moore	2021-03-05	1	-20/+32
\| \| \| \| \| \| \| \| \| \| \|	According to commentary on GCC bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99143, the alignment behavior of linker sections on which RTEMS has relied was never guaranteed to be consistent across platforms and any alignment requirements for linker sections needs to be enforced explicitly. This adds those explicit alignment requirements. Closes #4255.
*	Fix RTEMS_LINKER_ROSET_ITEM_ORDERED_DECLARE()	Sebastian Huber	2021-01-25	1	-1/+1
\| \| \| \| \| \|	Add "extern" similar to RTEMS_LINKER_RWSET_ITEM_ORDERED_DECLARE(). Close #4221.
*	score: Fix linker sets on small data area targets	Sebastian Huber	2020-02-06	1	-3/+13
\| \| \| \|	Update #3865.
*	linkersets: Revert to zero-length arrays	Sebastian Huber	2019-11-25	1	-18/+8
\| \| \| \| \| \| \| \| \|	This partially reverts commit 7ec08391fee73d7a25855089f4996f3c4f448007. Since the RTEMS_DEFINE_GLOBAL_SYMBOL_IN_SECTION() cannot control the alignment of the symbol it cannot be used to define the begin of a linker set. File scope basic __asm__ statements cannot have operands, so there is no way to specify the desired alignment.
*	linkersets: Avoid use of zero-length array	Sebastian Huber	2019-10-28	1	-12/+22
\| \| \| \|	Use RTEMS_DEFINE_GLOBAL_SYMBOL_IN_SECTION() instead.
*	Remove make preinstall	Chris Johns	2018-01-25	1	-0/+129
	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.