Studio:Understanding SCL conflicts - Revision history

Timd: Text replace - 'Category:Workarounds' to 'Category:Studio:Workarounds'

2009-08-21T00:13:07Z

Text replace - 'Category:Workarounds' to 'Category:Studio:Workarounds'

← Older revision		Revision as of 00:13, 21 August 2009
Line 40:		Line 40:
	... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )		... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )
	</pre>		</pre>
	[[Category:Workarounds]]		[[Category:Studio:Workarounds]]

Timd: Understanding SCL conflicts moved to Studio:Understanding SCL conflicts

2009-08-18T23:14:25Z

Understanding SCL conflicts moved to Studio:Understanding SCL conflicts

← Older revision	Revision as of 23:14, 18 August 2009
(No difference)

Robg at 18:17, 6 October 2008

2008-10-06T18:17:19Z

← Older revision		Revision as of 18:17, 6 October 2008
Line 1:		Line 1:
	There is a new class of conflicts reported by the compiler called SCL conflicts. These conflicts are caused when two or more top-level header files contain conflicting constant values or ~~pragmatized~~ types. These were silently ignored in previous versions of STRIDE.		There is a new class of conflicts reported by the compiler called SCL conflicts. These conflicts are caused when two or more top-level header files contain conflicting constant values or types that have had inconsistent pragmas applied between compilation units. These were silently ignored in previous versions of STRIDE.

	There are two types of SCL conflicts:		There are two types of SCL conflicts:

Timd at 00:32, 11 March 2008

2008-03-11T00:32:15Z

← Older revision		Revision as of 00:32, 11 March 2008
Line 1:		Line 1:
	There is a new class of conflicts reported by the compiler called SCL conflicts. These conflicts are caused when two or more top-level header files contain conflicting constant values or pragmatized types. These were silently ignored in previous versions of STRIDE.		There is a new class of conflicts reported by the compiler called SCL conflicts. These conflicts are caused when two or more top-level header files contain conflicting constant values or pragmatized types. These were silently ignored in previous versions of STRIDE.

	There are two types of SCL conflicts:~~<br>~~		There are two types of SCL conflicts:
	<ol>		<ol>
	<li>The value of an enumeration constant or numeric valued preprocessor macro is in conflict with the results of the compilation of two top-level header files. A warning will be issued indicating the name associated with the inconsistent values. The compilation will still be successful, as this is only a warning; however, the value for the constant stored in ascript.Constants() will be the string “ERROR_VALUE_CONFLICT” rather than either of the original conflicting numeric values. In previous versions of STRIDE, the second value was accepted by default.</li>		<li>The value of an enumeration constant or numeric valued preprocessor macro is in conflict with the results of the compilation of two top-level header files. A warning will be issued indicating the name associated with the inconsistent values. The compilation will still be successful, as this is only a warning; however, the value for the constant stored in ascript.Constants() will be the string “ERROR_VALUE_CONFLICT” rather than either of the original conflicting numeric values. In previous versions of STRIDE, the second value was accepted by default.</li>
	<li>A type, T, occurs in two different top-level header files and is structurally different in both. This structural difference can be caused by inconsistent or conflicting SCL pragmas applied to the type, or it can be caused by a C language difference between the types. This type of conflict is considered an error; therefore, the compilation fails and error message is returned.</li>		<li>A type, T, occurs in two different top-level header files and is structurally different in both. This structural difference can be caused by inconsistent or conflicting SCL pragmas applied to the type, or it can be caused by a C language difference between the types. This type of conflict is considered an error; therefore, the compilation fails and error message is returned.</li>
	~~<br>~~
	'''Example 1'''~~<br>~~		'''Example 1'''
	The following example uses two top-level header files, Header1.h and Header2.h.~~<br><br>~~		The following example uses two top-level header files, Header1.h and Header2.h.
	''Header1.h''		''Header1.h''
	<tt>#define A 1</~~tt><br~~>		<source lang="c">
			#define A 1
			</source>
	''Header2.h''		''Header2.h''
	<tt>#define A 2</~~tt><br~~>		<source lang="c">
	The compilation of workspace 1 (via Header1.h) will return a Merge Conflict warning for “A”. The compilation will still be successful; the value of “A” in ascript.Constants() will be the string “ERROR_VALUE_CONFLICT”.~~<br><br>~~		#define A 2
	'''Example 2'''~~<br>~~		</source>
	The following example uses two top-level header files, Header1.h and Header2.h, and one header file that is not a top-level header file, NotTopLevelHeader.h.~~<br><br>~~		The compilation of workspace 1 (via Header1.h) will return a Merge Conflict warning for “A”. The compilation will still be successful; the value of “A” in ascript.Constants() will be the string “ERROR_VALUE_CONFLICT”.
			'''Example 2'''
			The following example uses two top-level header files, Header1.h and Header2.h, and one header file that is not a top-level header file, NotTopLevelHeader.h.
	''Header1.h''		''Header1.h''
	<tt>#include "NotTopLevelHeader.h"~~<br>~~		<source lang="c">
	#pragma scl_ptr (S.p, OUT, PRIVATE);~~<br>~~		#include "NotTopLevelHeader.h"
	int f (S s);~~<br>~~		#pragma scl_ptr (S.p, OUT, PRIVATE);
	#pragma scl_function(f);~~<br>~~</tt>		int f (S s);
			#pragma scl_function(f);
			</source>
	''Header2.h''		''Header2.h''
	<tt>#include "NotTopLevelHeader.h"~~<br>~~		<source lang="c">
	int g (S s);~~<br>~~		#include "NotTopLevelHeader.h"
	#pragma scl_function(g);~~<br>~~</tt>		int g (S s);
			#pragma scl_function(g);
			</source>
	''NotTopLevelHeader.h''		''NotTopLevelHeader.h''
	<tt>typedef struct S {int *p;} S;</~~tt><br~~>		<source lang="c">
	As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>		typedef struct S {int *p;} S;
	~~<tt>~~... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>		</source>
			As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:
			<pre>
			... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )
			</pre>
	[[Category:Workarounds]]		[[Category:Workarounds]]

Timd at 18:07, 29 February 2008

2008-02-29T18:07:02Z

← Older revision		Revision as of 18:07, 29 February 2008
Line 28:		Line 28:
	As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>		As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>
	<tt>... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>		<tt>... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>
			[[Category:Workarounds]]

Root at 21:33, 5 February 2008

2008-02-05T21:33:49Z

← Older revision		Revision as of 21:33, 5 February 2008
Line 28:		Line 28:
	As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>		As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>
	<tt>... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>		<tt>... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>



	~~[[Category:Application Notes]]~~

Root at 23:45, 4 February 2008

2008-02-04T23:45:51Z

← Older revision		Revision as of 23:45, 4 February 2008
Line 31:		Line 31:


	[[Category:~~KB]]~~		[[Category:Application Notes]]
	~~[[Category:Troubleshooting]]~~
	~~[[Category:SCL~~]]

Andreo at 23:30, 28 November 2007

2007-11-28T23:30:50Z

← Older revision		Revision as of 23:30, 28 November 2007
Line 33:		Line 33:
	[[Category:KB]]		[[Category:KB]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]
			[[Category:SCL]]

Root at 23:00, 8 October 2007

2007-10-08T23:00:40Z

← Older revision		Revision as of 23:00, 8 October 2007
Line 32:		Line 32:

	[[Category:KB]]		[[Category:KB]]
			[[Category:Troubleshooting]]

Root at 22:56, 21 June 2007

2007-06-21T22:56:19Z

← Older revision		Revision as of 22:56, 21 June 2007
Line 28:		Line 28:
	As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>		As a result of the functions f() and g() having a different picture of the shared type S, the compilation fails and returns the following Merge Error:<br>
	<tt>... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>		<tt>... \header1.h(0) : Error : Merge conflict -- Found conflicting destinations for scl_ptr(S.p, ... )</tt>



			[[Category:KB]]