Bootstrapping - Revision history

Manus at 18:29, 26 June 2009

2009-06-26T18:29:06Z

← Older revision		Revision as of 18:29, 26 June 2009
Line 6:		Line 6:
	The general idea is that when you do a change in the code generation (often for improving the speed) you want to get a compiler that has been compiled with the new code generation to benefit from the changes.		The general idea is that when you do a change in the code generation (often for improving the speed) you want to get a compiler that has been compiled with the new code generation to benefit from the changes.

	==When not bootstrapping==		===When not bootstrapping===
	Although you can always do a bootstrap, there are cases when it is actually not required. For example when:		Although you can always do a bootstrap, there are cases when it is actually not required. For example when:
	* Changing an header file which will impact the C generated code in a non-intrusive way, but still requires a new runtime. In that case, no bootstrap is necessary, it suffices to copy the new header and runtime to the current delivery.		* Changing an header file which will impact the C generated code in a non-intrusive way, but still requires a new runtime. In that case, no bootstrap is necessary, it suffices to copy the new header and runtime to the current delivery.
	* Changing a kernel library class which does not involve a special compiler knowledge (e.g. fixing a routine of STRING).		* Changing a kernel library class which does not involve a special compiler knowledge (e.g. fixing a routine of STRING).


	==Bootstrapping the compiler==		==Bootstrapping the compiler==

Manus: /* Definition */

2009-06-26T18:26:04Z

Definition

← Older revision		Revision as of 18:26, 26 June 2009
Line 1:		Line 1:
	[[Category:Compiler]]		[[Category:Compiler]]
	==Definition==		==Definition==
	Check out the definition from ~~wikipedia~~ http://en.wikipedia.org/wiki/~~Bootstrapping~~ to know more about bootstrapping.		Check out the definition from [http://en.wikipedia.org/wiki/Bootstrapping_(compilers) Wikipedia] to know more about bootstrapping.

	==Why bootstrapping?==		==Why bootstrapping?==

Manus: Refer to Building a delivery page.

2006-11-02T00:26:06Z

Refer to Building a delivery page.

← Older revision		Revision as of 00:26, 2 November 2006
Line 36:		Line 36:

	==Building a delivery==		==Building a delivery==
	The above steps talk about building deliveries. ~~Below are~~ the instructions on how to build a minimal delivery in a directory called EiffelXX. ~~The following commands will only work if executed under bash.~~		The above steps talk about building deliveries. Follow [[Building_a_delivery\|the instructions on how to build a minimal delivery]] in a directory called EiffelXX.

	~~<pre>~~
	~~export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es/trunk~~
	~~mkdir EiffelXX~~
	~~export $NEW_ISE_EIFFEL=`pwd`/EiffelXX~~
	~~cd EiffelXX~~
	~~svn co $SVNURL/Delivery/studio~~
	~~svn co $SVNURL/Delivery/eifinit~~

	~~cd studio/config~~
	~~mv unix $ISE_PLATFORM~~
	~~cd ..~~

	~~cd studio/spec~~
	~~mkdir $ISE_PLATFORM~~
	~~mkdir $ISE_PLATFORM/bin~~
	~~mkdir $ISE_PLATFORM/include~~
	~~mkdir $ISE_PLATFORM/lib~~

	~~cp unix/* $ISE_PLATFORM/bin~~
	~~rm -rf unix~~

	~~cd $EIFFEL_SRC/C/run-time~~
	~~cp *.h $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/include~~
	~~cp ../config.sh $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/include~~
	~~cp lib* $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/lib~~
	~~cp x2c $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin~~
	~~cd ..~~
	~~cp ipc/daemon/estudio $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin~~
	~~</pre>~~

Manus: Use mv instead of cp.

2006-05-02T21:44:36Z

Use mv instead of cp.

← Older revision		Revision as of 21:44, 2 May 2006
Line 47:		Line 47:

	cd studio/config		cd studio/config
	~~mkdir $ISE_PLATFORM~~		mv unix $ISE_PLATFORM

	cp unix/* $ISE_PLATFORM
	cd ..		cd ..

DavidFlatz: studio/config needs to be copied to $ISE_PLATFORM too

2006-05-02T20:29:28Z

studio/config needs to be copied to $ISE_PLATFORM too

← Older revision		Revision as of 20:29, 2 May 2006
Line 45:		Line 45:
	svn co $SVNURL/Delivery/studio		svn co $SVNURL/Delivery/studio
	svn co $SVNURL/Delivery/eifinit		svn co $SVNURL/Delivery/eifinit

			cd studio/config
			mkdir $ISE_PLATFORM

			cp unix/* $ISE_PLATFORM
			cd ..

	cd studio/spec		cd studio/spec

Manus: Added small explanation on building a delivery

2006-05-02T19:43:25Z

Added small explanation on building a delivery

← Older revision		Revision as of 19:43, 2 May 2006
Line 34:		Line 34:

	Of course you restart the bootstrap process after find the cause of the error and fixing it.		Of course you restart the bootstrap process after find the cause of the error and fixing it.

			==Building a delivery==
			The above steps talk about building deliveries. Below are the instructions on how to build a minimal delivery in a directory called EiffelXX. The following commands will only work if executed under bash.

			<pre>
			export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es/trunk
			mkdir EiffelXX
			export $NEW_ISE_EIFFEL=`pwd`/EiffelXX
			cd EiffelXX
			svn co $SVNURL/Delivery/studio
			svn co $SVNURL/Delivery/eifinit

			cd studio/spec
			mkdir $ISE_PLATFORM
			mkdir $ISE_PLATFORM/bin
			mkdir $ISE_PLATFORM/include
			mkdir $ISE_PLATFORM/lib

			cp unix/* $ISE_PLATFORM/bin
			rm -rf unix

			cd $EIFFEL_SRC/C/run-time
			cp *.h $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/include
			cp ../config.sh $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/include
			cp lib* $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/lib
			cp x2c $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin
			cd ..
			cp ipc/daemon/estudio $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin
			</pre>

Manus: /* How do we find if it really worked? */

2006-04-10T13:59:48Z

How do we find if it really worked?

← Older revision		Revision as of 13:59, 10 April 2006
Line 31:		Line 31:
	{{Note\|By generated code we meant the C code because although the binaries should be exactly identical in size, they usually are not identical because most binary formats store a date in the binary and since they have not been compiled at the exact same time we cannot compare them.}}		{{Note\|By generated code we meant the C code because although the binaries should be exactly identical in size, they usually are not identical because most binary formats store a date in the binary and since they have not been compiled at the exact same time we cannot compare them.}}

	If ~~this is~~ not ~~the case~~, then something is not right in the new code generation or in the run-time/header files, and the bootstrap process needs to be restarted from the ''original ec'' and the ''orginal delivery''.		If they are not identical, then something is not right in the new code generation or in the run-time/header files, and the bootstrap process needs to be restarted from the ''original ec'' and the ''orginal delivery''.

	Of course you restart the bootstrap process after find the cause of the error and fixing it.		Of course you restart the bootstrap process after find the cause of the error and fixing it.

Manus: /* How do we find if it really worked? */

2006-04-10T13:58:38Z

How do we find if it really worked?

← Older revision		Revision as of 13:58, 10 April 2006
Line 27:		Line 27:

	===How do we find if it really worked?===		===How do we find if it really worked?===
	If everything went well, the generated code for ''ec_level2'' and ''ec_level3'' should be identical. If this is not the case, then something is not right in the new code generation or in the run-time/header files, and the bootstrap process needs to be restarted from the ''original ec'' and the ''orginal delivery''.		If everything went well, the generated code for ''ec_level2'' and ''ec_level3'' should be identical.

			{{Note\|By generated code we meant the C code because although the binaries should be exactly identical in size, they usually are not identical because most binary formats store a date in the binary and since they have not been compiled at the exact same time we cannot compare them.}}

			If this is not the case, then something is not right in the new code generation or in the run-time/header files, and the bootstrap process needs to be restarted from the ''original ec'' and the ''orginal delivery''.

	Of course you restart the bootstrap process after find the cause of the error and fixing it.		Of course you restart the bootstrap process after find the cause of the error and fixing it.

Manus: Added bootstrap description

2006-04-10T13:52:07Z

Added bootstrap description

← Older revision		Revision as of 13:52, 10 April 2006
Line 8:		Line 8:
	==When not bootstrapping==		==When not bootstrapping==
	Although you can always do a bootstrap, there are cases when it is actually not required. For example when:		Although you can always do a bootstrap, there are cases when it is actually not required. For example when:
	* Changing an header file which will impact the C generated code in a non-~~intruisive~~ way, but still requires a new runtime. In that case, no bootstrap is necessary, it suffices to copy the new header and runtime to the current delivery.		* Changing an header file which will impact the C generated code in a non-intrusive way, but still requires a new runtime. In that case, no bootstrap is necessary, it suffices to copy the new header and runtime to the current delivery.
	* Changing a kernel library class which does not involve a special compiler knowledge (e.g. fixing a routine of STRING).		* Changing a kernel library class which does not involve a special compiler knowledge (e.g. fixing a routine of STRING).

Line 14:		Line 14:
	==Bootstrapping the compiler==		==Bootstrapping the compiler==
	===Initial compiler===		===Initial compiler===
	To start the ~~boostrap~~ process you have to start from a working compiler, this is usually one of the released version. Let's call this compiler ''original ec'' and its delivery ''original_delivery''.		To start the bootstrap process you have to start from a working compiler, this is usually one of the released version. Let's call this compiler ''original ec'' and its delivery ''original_delivery''.

	===First step===		===First step===
	Using		Using ''original ec'' and the configuration file finalize a new ec, this version is called ''ec_level1''. This version is compiled with the header files and run-time of the ''original delivery''.

			===Second step===
			Compile a new run-time and copy the headers to a new delivery ''level1 delivery'', as well as the new ''ec_level1'' executable. Now repeat the first step, you now get a version called ''ec_level2''. This version is obviously compiled with the header files and run-time of the ''level11 delivery''.

			===Final step===
			Using the same ''level1 delivery'', but this time using the ''ec_level2'' executable, repeat the first step, you now get a version called ''ec_level3''. This version is also called the bootstrapped version.


			===How do we find if it really worked?===
			If everything went well, the generated code for ''ec_level2'' and ''ec_level3'' should be identical. If this is not the case, then something is not right in the new code generation or in the run-time/header files, and the bootstrap process needs to be restarted from the ''original ec'' and the ''orginal delivery''.

			Of course you restart the bootstrap process after find the cause of the error and fixing it.

Manus at 13:42, 10 April 2006

2006-04-10T13:42:25Z

← Older revision		Revision as of 13:42, 10 April 2006
Line 14:		Line 14:
	==Bootstrapping the compiler==		==Bootstrapping the compiler==
	===Initial compiler===		===Initial compiler===
	To start the boostrap process you have to start from a working compiler, this is usually one of the released version. Let's call this compiler ~~ec_original~~.		To start the boostrap process you have to start from a working compiler, this is usually one of the released version. Let's call this compiler ''original ec'' and its delivery ''original_delivery''.

			===First step===
			Using