Entry point - Revision history

Chekwob: 3 revisions imported: Initial import from Wikia

2019-04-27T17:44:33Z

3 revisions imported: Initial import from Wikia

38.132.187.136: /* start() */

2017-11-10T20:45:06Z

‎start()

Wikia>WurlyFox: links

2015-07-27T10:37:31Z

links

Wikia>WurlyFox: Created page with "An entry point locates the first section of code (subroutine) executed by a CPU after its source executable is loaded into main memory. A common symbolic name for the entry po..."

2015-07-25T04:29:47Z

Created page with "An entry point locates the first section of code (subroutine) executed by a CPU after its source executable is loaded into main memory. A common symbolic name for the entry po..."

New page

An entry point locates the first section of code (subroutine) executed by a CPU after its source executable is loaded into main memory. A common symbolic name for the entry point routine is <code>start</code>.

== Entry point locations ==
The following lists the location of the entry point for each of the Crash games:

*Crash 1 - 0x3E018

== start() ==
The <code>start</code> routine sets the location of the global pointer, initializes the heap, and calls the <code>main</code> routine.

== main() ==
The <code>main</code> routine calls 3 subroutines. The first of these routines performs hardware initialization. The second contains the main game loop. The third releases any resources allocated during hardware initialization. Prior to execution of these routines, the main loop condition at <code>0x56410</code> is set to true/1.

In each game, the level id for the 'initial level' is passed as an argument to the main loop routine. The initial level isn't actually a 'level' per-se, but rather a game state, which includes the title sequence, options menu, password menu (Crash 1), map (Crash 1), and game over screen.

← Older revision		Revision as of 20:45, 10 November 2017
Line 13:		Line 13:

	In each game, the level id for the 'initial level' is passed as an argument to the [[Game Loop\|game loop routine]]. The initial level isn't actually a 'level' per-se, but rather a game state, which includes the title sequence, options menu, password menu (Crash 1), map (Crash 1), and game over screen.		In each game, the level id for the 'initial level' is passed as an argument to the [[Game Loop\|game loop routine]]. The initial level isn't actually a 'level' per-se, but rather a game state, which includes the title sequence, options menu, password menu (Crash 1), map (Crash 1), and game over screen.
		+	__FORCETOC__
		+	__NEWSECTIONLINK__

← Older revision	Revision as of 17:44, 27 April 2019
(No difference)

@@ Line 10: / Line 10: @@
 == main() ==
-The <code>main</code> routine calls 3 subroutines. The first of these routines performs hardware initialization. The second contains the main game loop. The third releases any resources allocated during hardware initialization. Prior to execution of these routines, the main loop condition at <code>0x56410</code> is set to true/1.
+The <code>main</code> routine calls 3 subroutines. The first of these routines performs hardware initialization. The second contains the [[Game Loop|game loop]]. The third releases any resources allocated during hardware initialization. Prior to execution of these routines, the game loop condition at <code>0x56410</code> is set to true/1.
-In each game, the level id for the 'initial level' is passed as an argument to the main loop routine. The initial level isn't actually a 'level' per-se, but rather a game state, which includes the title sequence, options menu, password menu (Crash 1), map (Crash 1), and game over screen.
+In each game, the level id for the 'initial level' is passed as an argument to the [[Game Loop|game loop routine]]. The initial level isn't actually a 'level' per-se, but rather a game state, which includes the title sequence, options menu, password menu (Crash 1), map (Crash 1), and game over screen.