The Compiler - Revision history

Polas: 15 revisions imported

2019-04-15T15:45:00Z

15 revisions imported

Polas: /* Command line options */

2014-01-02T19:01:56Z

‎Command line options

Polas: /* Executable options */

2013-08-02T13:10:15Z

‎Executable options

Polas at 11:32, 26 July 2013

2013-07-26T11:32:44Z

Polas: /* Environment variables */

2013-02-23T18:36:39Z

‎Environment variables

Polas: /* Environment variables */

2013-02-07T14:47:14Z

‎Environment variables

Polas: /* Command line options */

2013-02-07T14:45:58Z

‎Command line options

Polas: /* Compilation in more detail */

2013-01-19T17:32:39Z

‎Compilation in more detail

Polas: /* Compilation in more detail */

2013-01-19T17:31:30Z

‎Compilation in more detail

Polas: /* Compilation in more detail */

2013-01-19T16:05:05Z

‎Compilation in more detail

@@ Line 24: / Line 24: @@
 * '''-cc''' ''Output C code only to stdout''
 * '''-e''' ''Display C compiler errors and warnings also''
 * '''-s''' ''Silent operation (no warnings)''
 * '''-summary''' ''Produce a summary of compilation''

@@ Line 59: / Line 59: @@
 == Executable options ==
-Once compiled, the resulting executable provides for a number of command line options which reports details of the runtime environment that it will operate under.
+Once compiled, the resulting executable provides for a number of command line options which reports details of the runtime environment that it will operate under. These will only be checked if the executable is run with one process.
 * '''--mesham_p''' ''Displays the minimum number of processes required to run the code''
 * '''--mesham_c''' ''Summary information about the communications layer, such as MPI, being used to link the processes''
 * '''--mesham_v''' ''Displays version information about the runtime library and also the compiled executable''

← Older revision		Revision as of 11:32, 26 July 2013
Line 56:		Line 56:

	Would set these four variables to those appropriate values, obviously change the values as required.		Would set these four variables to those appropriate values, obviously change the values as required.
		+
		+	== Executable options ==
		+
		+	Once compiled, the resulting executable provides for a number of command line options which reports details of the runtime environment that it will operate under.
		+
		+	* '''--mesham_p''' ''Displays the minimum number of processes required to run the code''
		+	* '''--mesham_c''' ''Summary information about the communications layer, such as MPI, being used to link the processes''
		+	* '''--mesham_v''' ''Displays version information about the runtime library and also the compiled executable''

@@ Line 43: / Line 43: @@
 * '''MESHAM_INCLUDE''' ''The optional location of any additional include files, separated via ;''
 * '''MESHAM_C_COMPILER''' ''The C compiler to use, mpicc is a common choice''
 * '''MESHAM_C_INCLUDE''' ''The location of header files for the C compiler to include, specifically mesham.h, separated via ;''
 * '''MESHAM_C_LIBRARY''' ''The location of libraries for the C compiler to link against, specifically the runtime library, separated via ;''

@@ Line 45: / Line 45: @@
 * '''MESHAM_C_INCLUDE''' ''The location of header files for the C compiler to include, specifically mesham.h, separated via ;''
 * '''MESHAM_C_LIBRARY''' ''The location of libraries for the C compiler to link against, specifically the runtime library, separated via ;''
 It is common to set these system variables in the ''bashrc'' script, which is commonly in your home directory. To do so then something like

← Older revision	Revision as of 15:45, 15 April 2019
(No difference)

@@ Line 34: / Line 34: @@
 * '''-v''' ''Display compiler version information''
 * '''-vt''' ''Display compiler and type version information''
 == Environment variables ==

@@ Line 13: / Line 13: @@
 The compiler itself is contained within a number of different phases. Firstly, your Mesham code goes through a preprocessor which will expand the directives (such as [[Include|include]]) into Mesham code. It is at the preprocessor stage that the standard function libraries are made available to the code if the programmer has included them. The code is then fed into the core compiler which contains the keywords and general rules of the language but does not contain any types. These types exist in a separate library and behaviour is called via an API, from the core compiler into the appropriate types.
-<center>[[File:Oubliettelandscape.png|400px]]</center>
+<center>[[File:Oubliettelandscape.png|500px]]</center>
 The [[Oubliette]] core produces non human readable ANSI C99 code as an intermediate representation (IR), which is then fed into an applicable C compiler. This stage is also performed by the compiler - although it is possible to dump out this C code and manually compiler if desired.

← Older revision		Revision as of 16:05, 19 January 2013
Line 12:		Line 12:

	The compiler itself is contained within a number of different phases. Firstly, your Mesham code goes through a preprocessor which will expand the directives (such as [[Include\|include]]) into Mesham code. It is at the preprocessor stage that the standard function libraries are made available to the code if the programmer has included them. The code is then fed into the core compiler which contains the keywords and general rules of the language but does not contain any types. These types exist in a separate library and behaviour is called via an API, from the core compiler into the appropriate types.		The compiler itself is contained within a number of different phases. Firstly, your Mesham code goes through a preprocessor which will expand the directives (such as [[Include\|include]]) into Mesham code. It is at the preprocessor stage that the standard function libraries are made available to the code if the programmer has included them. The code is then fed into the core compiler which contains the keywords and general rules of the language but does not contain any types. These types exist in a separate library and behaviour is called via an API, from the core compiler into the appropriate types.
		+
		+	<center>[[File:Oubliettelandscape.png\|500px]]</center>

	The [[Oubliette]] core produces non human readable ANSI C99 code as an intermediate representation (IR), which is then fed into an applicable C compiler. This stage is also performed by the compiler - although it is possible to dump out this C code and manually compiler if desired.		The [[Oubliette]] core produces non human readable ANSI C99 code as an intermediate representation (IR), which is then fed into an applicable C compiler. This stage is also performed by the compiler - although it is possible to dump out this C code and manually compiler if desired.