Squashed commit of the sb-vbs branch.

Includes the SD-VBS benchmarks modified to: - Use libextra to loop as realtime jobs - Preallocate memory before starting their main computation - Accept input via stdin instead of via argc Does not include the SD-VBS matlab code. Fixes libextra execution in LITMUS^RT.
author: Leo Chan <leochanj@live.unc.edu> 2020-10-22 01:53:21 -0400
committer: Joshua Bakita <jbakita@cs.unc.edu> 2020-10-22 01:56:35 -0400
commit: d17b33131c14864bd1eae275f49a3f148e21cf29 (patch)
tree: 0d8f77922e8d193cb0f6edab83018f057aad64a0 /SD-VBS/portability
parent: 601ed25a4c5b66cb75315832c15613a727db2c26 (diff)
3 files changed, 185 insertions, 0 deletions
diff --git a/SD-VBS/portability/386-gcc.h b/SD-VBS/portability/386-gcc.h
new file mode 100644
index 0000000..91c95a6
--- /dev/null
+++ b/SD-VBS/portability/386-gcc.h
@@ -0,0 +1,80 @@
+/*
+-------------------------------------------------------------------------------
+One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined.
+-------------------------------------------------------------------------------
+*/
+#define LITTLEENDIAN
+/*
+-------------------------------------------------------------------------------
+The macro `BITS64' can be defined to indicate that 64-bit integer types are
+supported by the compiler.
+-------------------------------------------------------------------------------
+*/
+#define BITS64
+/*
+-------------------------------------------------------------------------------
+Each of the following `typedef's defines the most convenient type that holds
+integers of at least as many bits as specified.  For example, `uint8' should
+be the most convenient type that can hold unsigned integers of as many as
+8 bits.  The `flag' type must be able to hold either a 0 or 1.  For most
+implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
+to the same as `int'.
+-------------------------------------------------------------------------------
+*/
+typedef char flag;
+typedef unsigned char uint8;
+typedef signed char int8;
+typedef int uint16;
+typedef int int16;
+typedef unsigned int uint32;
+typedef signed int int32;
+#ifdef BITS64
+typedef unsigned long long int uint64;
+typedef signed long long int int64;
+#endif
+/*
+-------------------------------------------------------------------------------
+Each of the following `typedef's defines a type that holds integers
+of _exactly_ the number of bits specified.  For instance, for most
+implementation of C, `bits16' and `sbits16' should be `typedef'ed to
+`unsigned short int' and `signed short int' (or `short int'), respectively.
+-------------------------------------------------------------------------------
+*/
+typedef unsigned char bits8;
+typedef signed char sbits8;
+typedef unsigned short int bits16;
+typedef signed short int sbits16;
+typedef unsigned int bits32;
+typedef signed int sbits32;
+#ifdef BITS64
+typedef unsigned long long int bits64;
+typedef signed long long int sbits64;
+#endif
+#ifdef BITS64
+/*
+-------------------------------------------------------------------------------
+The `LIT64' macro takes as its argument a textual integer literal and
+if necessary ``marks'' the literal as having a 64-bit integer type.
+For example, the GNU C Compiler (`gcc') requires that 64-bit literals be
+appended with the letters `LL' standing for `long long', which is `gcc's
+name for the 64-bit integer type.  Some compilers may allow `LIT64' to be
+defined as the identity macro:  `#define LIT64( a ) a'.
+-------------------------------------------------------------------------------
+*/
+#define LIT64( a ) a##LL
+#endif
+/*
+-------------------------------------------------------------------------------
+The macro `INLINE' can be used before functions that should be inlined.  If
+a compiler does not support explicit inlining, this macro should be defined
+to be `static'.
+-------------------------------------------------------------------------------
+*/
+#define INLINE extern inline
diff --git a/SD-VBS/portability/SPARC-gcc.h b/SD-VBS/portability/SPARC-gcc.h
new file mode 100644
index 0000000..f926615
--- /dev/null
+++ b/SD-VBS/portability/SPARC-gcc.h
@@ -0,0 +1,80 @@
+/*
+-------------------------------------------------------------------------------
+One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined.
+-------------------------------------------------------------------------------
+*/
+#define BIGENDIAN
+/*
+-------------------------------------------------------------------------------
+The macro `BITS64' can be defined to indicate that 64-bit integer types are
+supported by the compiler.
+-------------------------------------------------------------------------------
+*/
+#define BITS64
+/*
+-------------------------------------------------------------------------------
+Each of the following `typedef's defines the most convenient type that holds
+integers of at least as many bits as specified.  For example, `uint8' should
+be the most convenient type that can hold unsigned integers of as many as
+8 bits.  The `flag' type must be able to hold either a 0 or 1.  For most
+implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
+to the same as `int'.
+-------------------------------------------------------------------------------
+*/
+typedef int flag;
+typedef int uint8;
+typedef int int8;
+typedef int uint16;
+typedef int int16;
+typedef unsigned int uint32;
+typedef signed int int32;
+#ifdef BITS64
+typedef unsigned long long int uint64;
+typedef signed long long int int64;
+#endif
+/*
+-------------------------------------------------------------------------------
+Each of the following `typedef's defines a type that holds integers
+of _exactly_ the number of bits specified.  For instance, for most
+implementation of C, `bits16' and `sbits16' should be `typedef'ed to
+`unsigned short int' and `signed short int' (or `short int'), respectively.
+-------------------------------------------------------------------------------
+*/
+typedef unsigned char bits8;
+typedef signed char sbits8;
+typedef unsigned short int bits16;
+typedef signed short int sbits16;
+typedef unsigned int bits32;
+typedef signed int sbits32;
+#ifdef BITS64
+typedef unsigned long long int bits64;
+typedef signed long long int sbits64;
+#endif
+#ifdef BITS64
+/*
+-------------------------------------------------------------------------------
+The `LIT64' macro takes as its argument a textual integer literal and
+if necessary ``marks'' the literal as having a 64-bit integer type.
+For example, the GNU C Compiler (`gcc') requires that 64-bit literals be
+appended with the letters `LL' standing for `long long', which is `gcc's
+name for the 64-bit integer type.  Some compilers may allow `LIT64' to be
+defined as the identity macro:  `#define LIT64( a ) a'.
+-------------------------------------------------------------------------------
+*/
+#define LIT64( a ) a##LL
+#endif
+/*
+-------------------------------------------------------------------------------
+The macro `INLINE' can be used before functions that should be inlined.  If
+a compiler does not support explicit inlining, this macro should be defined
+to be `static'.
+-------------------------------------------------------------------------------
+*/
+#define INLINE extern inline
diff --git a/SD-VBS/portability/portability.txt b/SD-VBS/portability/portability.txt
new file mode 100644
index 0000000..19335de
--- /dev/null
+++ b/SD-VBS/portability/portability.txt
@@ -0,0 +1,25 @@
+The SD-VBS suite is designed to be portable across different platforms. If you would like 
+port it, you need to set appropriate platform specific commands.
+By default, SD-VBS is set to the x86-64 bit architecture for the Linux operating system. The platform
+specific commands for this configuration can be found in SD-VBS/Portability/386-gcc.h. This configuration
+file is included in SD-VBS/Makefile.common.
+To change the platform specific commands:
+1. Modify/Add <Architecture>-gcc.h file appropriately
+2. Include <Architecture>-gcc.h file in SD-VBS/Makefile.common
+We have included a few sample configuration files in SD-VBS/Portability directory.
+These correspond to:
+1. x386 architecture, 32-64 bit
+3. SPARC architecture, 32-64 bit
+Note:
+SD-VBS has been tested on x86 32-bit and 64-bit architectures. If the user encounters undesired behavior
+while running the SD-VBS on other platforms, please report the bugs to:
+Sravanthi Kota Venkata: <skotavenkata@cs.ucsd.edu>
author	Leo Chan <leochanj@live.unc.edu>	2020-10-22 01:53:21 -0400
committer	Joshua Bakita <jbakita@cs.unc.edu>	2020-10-22 01:56:35 -0400
commit	d17b33131c14864bd1eae275f49a3f148e21cf29 (patch)
tree	0d8f77922e8d193cb0f6edab83018f057aad64a0 /SD-VBS/portability
parent	601ed25a4c5b66cb75315832c15613a727db2c26 (diff)

diff --git a/SD-VBS/portability/386-gcc.h b/SD-VBS/portability/386-gcc.h new file mode 100644 index 0000000..91c95a6 --- /dev/null +++ b/SD-VBS/portability/386-gcc.h
@@ -0,0 +1,80 @@
	1
	2	/*
	3	-------------------------------------------------------------------------------
	4	One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined.
	5	-------------------------------------------------------------------------------
	6	*/
	7	#define LITTLEENDIAN
	8
	9	/*
	10	-------------------------------------------------------------------------------
	11	The macro `BITS64' can be defined to indicate that 64-bit integer types are
	12	supported by the compiler.
	13	-------------------------------------------------------------------------------
	14	*/
	15	#define BITS64
	16
	17	/*
	18	-------------------------------------------------------------------------------
	19	Each of the following `typedef's defines the most convenient type that holds
	20	integers of at least as many bits as specified. For example, `uint8' should
	21	be the most convenient type that can hold unsigned integers of as many as
	22	8 bits. The `flag' type must be able to hold either a 0 or 1. For most
	23	implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
	24	to the same as `int'.
	25	-------------------------------------------------------------------------------
	26	*/
	27	typedef char flag;
	28	typedef unsigned char uint8;
	29	typedef signed char int8;
	30	typedef int uint16;
	31	typedef int int16;
	32	typedef unsigned int uint32;
	33	typedef signed int int32;
	34	#ifdef BITS64
	35	typedef unsigned long long int uint64;
	36	typedef signed long long int int64;
	37	#endif
	38
	39	/*
	40	-------------------------------------------------------------------------------
	41	Each of the following `typedef's defines a type that holds integers
	42	of _exactly_ the number of bits specified. For instance, for most
	43	implementation of C, `bits16' and `sbits16' should be `typedef'ed to
	44	`unsigned short int' and `signed short int' (or `short int'), respectively.
	45	-------------------------------------------------------------------------------
	46	*/
	47	typedef unsigned char bits8;
	48	typedef signed char sbits8;
	49	typedef unsigned short int bits16;
	50	typedef signed short int sbits16;
	51	typedef unsigned int bits32;
	52	typedef signed int sbits32;
	53	#ifdef BITS64
	54	typedef unsigned long long int bits64;
	55	typedef signed long long int sbits64;
	56	#endif
	57
	58	#ifdef BITS64
	59	/*
	60	-------------------------------------------------------------------------------
	61	The `LIT64' macro takes as its argument a textual integer literal and
	62	if necessary ``marks'' the literal as having a 64-bit integer type.
	63	For example, the GNU C Compiler (`gcc') requires that 64-bit literals be
	64	appended with the letters `LL' standing for `long long', which is `gcc's
	65	name for the 64-bit integer type. Some compilers may allow `LIT64' to be
	66	defined as the identity macro: `#define LIT64( a ) a'.
	67	-------------------------------------------------------------------------------
	68	*/
	69	#define LIT64( a ) a##LL
	70	#endif
	71
	72	/*
	73	-------------------------------------------------------------------------------
	74	The macro `INLINE' can be used before functions that should be inlined. If
	75	a compiler does not support explicit inlining, this macro should be defined
	76	to be `static'.
	77	-------------------------------------------------------------------------------
	78	*/
	79	#define INLINE extern inline
	80


diff --git a/SD-VBS/portability/SPARC-gcc.h b/SD-VBS/portability/SPARC-gcc.h new file mode 100644 index 0000000..f926615 --- /dev/null +++ b/SD-VBS/portability/SPARC-gcc.h
@@ -0,0 +1,80 @@
	1
	2	/*
	3	-------------------------------------------------------------------------------
	4	One of the macros `BIGENDIAN' or `LITTLEENDIAN' must be defined.
	5	-------------------------------------------------------------------------------
	6	*/
	7	#define BIGENDIAN
	8
	9	/*
	10	-------------------------------------------------------------------------------
	11	The macro `BITS64' can be defined to indicate that 64-bit integer types are
	12	supported by the compiler.
	13	-------------------------------------------------------------------------------
	14	*/
	15	#define BITS64
	16
	17	/*
	18	-------------------------------------------------------------------------------
	19	Each of the following `typedef's defines the most convenient type that holds
	20	integers of at least as many bits as specified. For example, `uint8' should
	21	be the most convenient type that can hold unsigned integers of as many as
	22	8 bits. The `flag' type must be able to hold either a 0 or 1. For most
	23	implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
	24	to the same as `int'.
	25	-------------------------------------------------------------------------------
	26	*/
	27	typedef int flag;
	28	typedef int uint8;
	29	typedef int int8;
	30	typedef int uint16;
	31	typedef int int16;
	32	typedef unsigned int uint32;
	33	typedef signed int int32;
	34	#ifdef BITS64
	35	typedef unsigned long long int uint64;
	36	typedef signed long long int int64;
	37	#endif
	38
	39	/*
	40	-------------------------------------------------------------------------------
	41	Each of the following `typedef's defines a type that holds integers
	42	of _exactly_ the number of bits specified. For instance, for most
	43	implementation of C, `bits16' and `sbits16' should be `typedef'ed to
	44	`unsigned short int' and `signed short int' (or `short int'), respectively.
	45	-------------------------------------------------------------------------------
	46	*/
	47	typedef unsigned char bits8;
	48	typedef signed char sbits8;
	49	typedef unsigned short int bits16;
	50	typedef signed short int sbits16;
	51	typedef unsigned int bits32;
	52	typedef signed int sbits32;
	53	#ifdef BITS64
	54	typedef unsigned long long int bits64;
	55	typedef signed long long int sbits64;
	56	#endif
	57
	58	#ifdef BITS64
	59	/*
	60	-------------------------------------------------------------------------------
	61	The `LIT64' macro takes as its argument a textual integer literal and
	62	if necessary ``marks'' the literal as having a 64-bit integer type.
	63	For example, the GNU C Compiler (`gcc') requires that 64-bit literals be
	64	appended with the letters `LL' standing for `long long', which is `gcc's
	65	name for the 64-bit integer type. Some compilers may allow `LIT64' to be
	66	defined as the identity macro: `#define LIT64( a ) a'.
	67	-------------------------------------------------------------------------------
	68	*/
	69	#define LIT64( a ) a##LL
	70	#endif
	71
	72	/*
	73	-------------------------------------------------------------------------------
	74	The macro `INLINE' can be used before functions that should be inlined. If
	75	a compiler does not support explicit inlining, this macro should be defined
	76	to be `static'.
	77	-------------------------------------------------------------------------------
	78	*/
	79	#define INLINE extern inline
	80


diff --git a/SD-VBS/portability/portability.txt b/SD-VBS/portability/portability.txt new file mode 100644 index 0000000..19335de --- /dev/null +++ b/SD-VBS/portability/portability.txt
@@ -0,0 +1,25 @@
	1	The SD-VBS suite is designed to be portable across different platforms. If you would like
	2	port it, you need to set appropriate platform specific commands.
	3
	4	By default, SD-VBS is set to the x86-64 bit architecture for the Linux operating system. The platform
	5	specific commands for this configuration can be found in SD-VBS/Portability/386-gcc.h. This configuration
	6	file is included in SD-VBS/Makefile.common.
	7
	8	To change the platform specific commands:
	9	1. Modify/Add <Architecture>-gcc.h file appropriately
	10	2. Include <Architecture>-gcc.h file in SD-VBS/Makefile.common
	11
	12	We have included a few sample configuration files in SD-VBS/Portability directory.
	13	These correspond to:
	14
	15	1. x386 architecture, 32-64 bit
	16	3. SPARC architecture, 32-64 bit
	17
	18	Note:
	19
	20	SD-VBS has been tested on x86 32-bit and 64-bit architectures. If the user encounters undesired behavior
	21	while running the SD-VBS on other platforms, please report the bugs to:
	22
	23	Sravanthi Kota Venkata: <skotavenkata@cs.ucsd.edu>
	24
	25