<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<!-- MHonArc v2.6.10 -->
	<channel>
		<title>news.eclipse.dsdp.rtsc</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/maillist.html</link>
		<description>NewsGroup: news.eclipse.dsdp.rtsc</description>
		<language>en-us</language>
		<pubDate>Thu, 10 Sep 2009 18:22:40 GMT</pubDate>
		<lastBuildDate>Thu, 10 Sep 2009 18:22:40 GMT</lastBuildDate>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		<generator>MHonArc RSS 2.0 RCFile</generator>
		<managingEditor>webmaster@eclipse.org (Webmaster)</managingEditor>
		<webMaster>webmaster@eclipse.org (Webmaster)</webMaster>
		<image>
			<title>news.eclipse.dsdp.rtsc</title>
			<url>http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg</url>
			<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/maillist.html</link>
		</image>
 

	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Object &amp; Target Specific Build Options?</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00249.html</link>
		<description>Anthony, you probably created your target from some of the existing targets. Most of the targets have the configuration parameter 'asmOpts'. You could add following to your target in config.bld ONLY when you build BIOS 6. targ.asmOpts.suffix = &amp;quot;-P -imacros...</description>
		<content:encoded><![CDATA[<tt>Anthony,<br>
you probably created your target from some of the existing targets. Most 
of the targets have the configuration parameter 'asmOpts'. You could add 
following to your target in config.bld ONLY when you build BIOS 6.</tt><br>
<br>
<tt>targ.asmOpts.suffix = &quot;-P -imacros=package/internal/$(subst 
_asm,,$(basename $(notdir $@))).xdc.h -x assembler-with-cpp&quot;;</tt><br>
<br>
<tt>I haven't really tested if the make function calls I used are just right, 
so you might need to make some edits but you can tell where I am going 
with it.</tt><br>
<br>
<tt>This is a hack that relies on knowing what's inside our generated 
makefiles, so if you decide to try it, you probably want to use it only 
until the BIOS 6 build system adds some options to let you specify per 
file command line options.</tt><br>
<br>
<pre style="margin: 0em;"><br></pre><br>
]]></content:encoded>
		<pubDate>Thu, 10 Sep 2009 18:09:58 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00249.html</guid>
		<author>sascha@xxxxxxx (Sasha Slijepcevic)</author>
	</item>
	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Object &amp; Target Specific Build Options?</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00248.html</link>
		<description>This question isprobably best answered by the BIOS team, but I'll give it a shot below (and forward this question to them). [snip] It might be easier to include this option for all objects and structure the header to only conditionally define macros for th...</description>
		<content:encoded><![CDATA[<pre style="margin: 0em;">comments embedded below</pre><br>
<tt>Anthony Seely wrote:
</tt><blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><tt>I am trying to compile BIOS V6 as from CCSV4 with a bare-metal arm-gcc 
toolchain (4.4.1) and binutils (2.19).
</tt></blockquote><tt><br>This question isprobably best answered by the BIOS team, but I'll give 
it a shot below (and forward this question to them).</tt><br>
<br>
<pre style="margin: 0em;">[snip]</pre><br>
<blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><tt>For about six assembly files, there is a *specific* include that is needed.<br>
For example the file Cache_asm.s needs to include 
package/internal/Cache.xdc.h<br>
Whereas the file HwiCommon_asm.s needs to incldue 
package/internal/HwiCommon.xdc.h.</tt><br>
<br>
<tt>In other words, for each of these five assembly files, I need to run gcc 
with a specific '-imacros &lt;filename&gt;'.<br>
I'm imagining there may be a way to set a target specific 'copts' attribute<br>
- and in fact there are examples of how to do this in the RTSC help in the<br>
Library.addObjects() function.<br>
BUT there are a couple catches.<br>
First catch - is I need to do this only for targets where I've changed the<br>
extension from .s470 (TI 470 assembler) to .sBMArmR4 (gcc bare-metal ARM 
R4 target).  
Right now I've followed other examples in the BIOS tree and only used the<br>
file basename in the 'objects' list.  The local gcc bare-metal ARM R4 
target<br>
matches files with extension .sBMArmR4 and only *those* files are the ones<br>
I need to add the -imacro header.h file name to.</tt><br>
<br>
<tt>Second catch, the build environment for BIOS includes a common build script<br>
that adds all the objects in object list to the library.<br>
So it will already have been added to the library with Library.addObject()<br>
and *after the fact* I'd need to add a specific header file to the gcc 
command line for each of the individual assembly files.</tt><br>
<br>
<tt>I'm looking for some suggestions on how this might be accomplished; or 
maybe<br>
an idea on a different way to tackle the issue.
</tt></blockquote><tt><br>It might be easier to include this option for all objects and structure 
the header to only conditionally define macros for the specific target 
you've created.</tt><br>
<br>
<tt>If your target follows the pattern of other targets there are a number 
of target-specific macros that are defined for any file including std.h; 
<a  href="http://rtsc.eclipse.org/cdoc-tip/xdc/package.html#xdoc-sect-5">http://rtsc.eclipse.org/cdoc-tip/xdc/package.html#xdoc-sect-5</a></tt><br>
<br>
<tt>In particular, if your target is ti.targets.arm.BMArmR4 you can create a 
header like the following:<br>
    #ifdef ti_targets_arm_BMArmR4<br>
        :<br>
    #endif</tt><br>
<br>
<tt>You can also include #ifdef that reference symbols defined by your 
compiler.  In this way the header can safely be included by _all_ files 
and you do not need to apply the -macros option selectively.</tt><br>
<br>
<pre style="margin: 0em;">But, again, the BIOS team might have a better answer for their build setup.</pre><br>
<br>
]]></content:encoded>
		<pubDate>Thu, 10 Sep 2009 15:01:37 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00248.html</guid>
		<author>d-russo@xxxxxxx (dave russo)</author>
	</item>


	<item>
		<title>[news.eclipse.dsdp.rtsc] Object &amp; Target Specific Build Options?</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00247.html</link>
		<description>I am trying to compile BIOS V6 as from CCSV4 with a bare-metal arm-gcc toolchain (4.4.1) and binutils (2.19). BIOS has a few assembly language files that include &amp;quot;C&amp;quot; header files with a line in the assembly source containing a directive &amp;quot;.CDECLS ... header...</description>
		<content:encoded><![CDATA[<tt>I am trying to compile BIOS V6 as from CCSV4 with a bare-metal arm-gcc 
toolchain (4.4.1) and binutils (2.19). </tt><br>
<br>
<pre style="margin: 0em;">BIOS has a few assembly language files that include &quot;C&quot; header files with a
line in the assembly source containing a directive &quot;.CDECLS ... header.h&quot;</pre><br>
<tt>This is a feature of the TI assembler that will allow the use of macro 
definitions from C header files.</tt><br>
<br>
<tt>I don't see any equivalent *directive* in GAS.  You can use a 
include directive but that's not for &quot;C&quot; it's for assembly.</tt><br>
<br>
<tt>However, you can invoke gcc with the following options:<br>
-P -imacros=headerfile -x assembler-with-cpp<br>
And it has the same effect as the TI .CDECLS directive. 
The C header is preprocessed but only macro definitions are set, 
there is no other output (not even comments -P) then the assembler is run.</tt><br>
<br>
<pre style="margin: 0em;">That much is ok.  I've tried this from the command line and it works fine.</pre><br>
<pre style="margin: 0em;">My problem now is to get the same effect through the XDC build script.</pre><br>
<tt>For about six assembly files, there is a *specific* include that is needed.<br>
For example the file Cache_asm.s needs to include 
package/internal/Cache.xdc.h<br>
Whereas the file HwiCommon_asm.s needs to incldue 
package/internal/HwiCommon.xdc.h.</tt><br>
<br>
<tt>In other words, for each of these five assembly files, I need to run gcc 
with a specific '-imacros &lt;filename&gt;'. </tt><br>
<br>
<tt>I'm imagining there may be a way to set a target specific 'copts' attribute<br>
- and in fact there are examples of how to do this in the RTSC help in the<br>
Library.addObjects() function. </tt><br>
<br>
<tt>BUT there are a couple catches. </tt><br>
<br>
<tt>First catch - is I need to do this only for targets where I've changed the<br>
extension from .s470 (TI 470 assembler) to .sBMArmR4 (gcc bare-metal ARM 
R4 target).   </tt><br>
<br>
<tt>Right now I've followed other examples in the BIOS tree and only used the<br>
file basename in the 'objects' list.  The local gcc bare-metal ARM R4 
target<br>
matches files with extension .sBMArmR4 and only *those* files are the ones<br>
I need to add the -imacro header.h file name to.</tt><br>
<br>
<tt>Second catch, the build environment for BIOS includes a common build script<br>
that adds all the objects in object list to the library.<br>
So it will already have been added to the library with Library.addObject()<br>
and *after the fact* I'd need to add a specific header file to the gcc 
command line for each of the individual assembly files.</tt><br>
<br>
<tt>I'm looking for some suggestions on how this might be accomplished; or 
maybe<br>
an idea on a different way to tackle the issue.</tt><br>
<br>
<tt> </tt><br>
<br>
<pre style="margin: 0em;"><br></pre><br>
]]></content:encoded>
		<pubDate>Wed, 09 Sep 2009 18:58:38 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00247.html</guid>
		<author>a-seely@xxxxxxx (Anthony Seely)</author>
	</item>


	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Finding out the size of the structure	in xs file</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00246.html</link>
		<description> </description>
		<content:encoded><![CDATA[<pre style="margin: 0em;">Yes.  See <a  href="http://rtsc.eclipse.org/docs-tip/XDCscript_-_Struct-Object.$sizeof">http://rtsc.eclipse.org/docs-tip/XDCscript_-_Struct-Object.$sizeof</a></pre><br>
<tt><br>Ravindranath wrote:
</tt><blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><tt>Is there a way to find out the size of the structure (declared in xdc 
file) in module's xs file.<br>
for example  i have  a structure<br>
like below in xdc file</tt><br>
<br>
<pre style="margin: 0em;">module xdc file</pre><br>
<pre style="margin: 0em;">struct entry
{
    UInt32 a;
    uinon {
       UInt8 b;
       UInt32 c;
    }
};</pre><br>
<pre style="margin: 0em;"><br>In xs file i have to  know the size of &lt;mod&gt;_entry structure size.</pre><br>
<pre style="margin: 0em;">How do i do this. Please let me know if any body knows  how to do it?.</pre><br>
</blockquote><br>
]]></content:encoded>
		<pubDate>Tue, 08 Sep 2009 14:26:28 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00246.html</guid>
		<author>d-russo@xxxxxxx (dave russo)</author>
	</item>
	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Using GateSwi_Handle_upCast</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00245.html</link>
		<description> </description>
		<content:encoded><![CDATA[<tt><br>Upcasting is unnecessary in the meta-domain since type checking occurs 
at runtime; in the target domain, excepts for very specialized 
situations, all type checks are preformed by the compiler.</tt><br>
<br>
<tt>Ravindranath wrote:
</tt><blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><pre style="margin: 0em;">Is it allowed to call  some thing like below in module's xs file.</pre><br>
<pre style="margin: 0em;">GateSwi.Handle handle;
handle = GateSwi.create();
handle = GateSwi.Handle_upCast(handle);</pre><br>
<pre style="margin: 0em;">Regards,
Ravindranth Andela</pre><br>
</blockquote><br>
]]></content:encoded>
		<pubDate>Tue, 08 Sep 2009 14:24:12 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00245.html</guid>
		<author>d-russo@xxxxxxx (dave russo)</author>
	</item>


	<item>
		<title>[news.eclipse.dsdp.rtsc] Finding out the size of the structure in	xs file</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00244.html</link>
		<description>Is there a way to find out the size of the structure (declared in xdc file) in module's xs file. for example i have a structure like below in xdc file module xdc file struct entry { UInt32 a; uinon { UInt8 b; UInt32 c; } }; In xs file i have to know the si...</description>
		<content:encoded><![CDATA[<tt>Is there a way to find out the size of the structure (declared in xdc 
file) 
in module's xs file.<br>
for example  i have  a structure<br>
like below in xdc file</tt><br>
<br>
<pre style="margin: 0em;">module xdc file</pre><br>
<pre style="margin: 0em;">struct entry
{
    UInt32 a;
    uinon {
       UInt8 b;
       UInt32 c;
    }
};</pre><br>
<pre style="margin: 0em;"><br>In xs file i have to  know the size of &lt;mod&gt;_entry structure size.</pre><br>
<pre style="margin: 0em;">How do i do this. Please let me know if any body knows  how to do it?.</pre><br>
<br>
]]></content:encoded>
		<pubDate>Fri, 04 Sep 2009 13:39:59 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00244.html</guid>
		<author>ravindranath.a@xxxxxxx (Ravindranath )</author>
	</item>


	<item>
		<title>[news.eclipse.dsdp.rtsc] Using GateSwi_Handle_upCast</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00243.html</link>
		<description>Is it allowed to call some thing like below in module's xs file. GateSwi.Handle handle; handle = GateSwi.create(); handle = GateSwi.Handle_upCast(handle); Regards, Ravindranth Andela </description>
		<content:encoded><![CDATA[<pre style="margin: 0em;">Is it allowed to call  some thing like below in module's xs file.</pre><br>
<tt>GateSwi.Handle handle;<br>
handle = GateSwi.create();<br>
handle = GateSwi.Handle_upCast(handle); </tt><br>
<br>
<pre style="margin: 0em;"><br>Regards,
Ravindranth Andela</pre><br>
<br>
]]></content:encoded>
		<pubDate>Wed, 02 Sep 2009 18:25:24 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00243.html</guid>
		<author>ravindranath.a@xxxxxxx (Ravindranath )</author>
	</item>


	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Issue with declaring structure variable and array under instance label in xdc fi</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00242.html</link>
		<description> </description>
		<content:encoded><![CDATA[<pre style="margin: 0em;">If I understand what you're looking for, I don't believe it's possible.</pre><br>
<tt>It sounds like you want specify the size of a module instance's creation 
parameters at configuration time.  For example</tt><br>
<br>
<pre style="margin: 0em;">Mod.xdc:
    module Mod {
        config Int ARR_SIZE = 2;
    instance:
        config Int myArr[ARR_SIZE] = [0, 0];
    }</pre><br>
<pre style="margin: 0em;">User's .cfg script:
    var Mod = xdc.useModule(&quot;...Mod&quot;);
    Mod.ARR_SIZE = 10;</pre><br>
<pre style="margin: 0em;">User's .c code:
    main() {
        Mod_Params params;
        Mod_Handle inst;</pre><br>
<pre style="margin: 0em;">        Mod_Params_init(&amp;params);
        for (i = 0; i &lt; Mod_ARR_SIZE; i++) {
            params.myArr[i] = i;  /* ERROR: myArr has just 2 elements */
        }
        inst = Mod_create(&amp;params, NULL);
    }</pre><br>
<tt>But the .c file is, in general, compiled before the configuration script 
is run.  As a result, the space allocated by the compiler on the stack 
for params (i.e., sizeof(Mod_Params)), can't change as the result of 
configuration.</tt><br>
<br>
<tt>An alternative might be to &quot;allocate&quot; the array in the instance object 
itself and allow the user to initialize this array via an instance 
method, say Mod_initArray().  The params structure can be initialized to 
a default array whose size and values are controlled by config 
parameters.  This makes the instance usable even if the user does not 
call Mod_initArray().</tt><br>
<br>
<pre style="margin: 0em;">User's .c code:
    Int myArr[10] = [1, ...];</pre><br>
<pre style="margin: 0em;">    main() {
        Mod_Params params;
        Mod_Handle inst;</pre><br>
<pre style="margin: 0em;">        Mod_Params_init(&amp;params);
        inst = Mod_create(&amp;params, NULL);
        Mod_initArray(inst, myArr, sizeof(arr));
    }</pre><br>
<tt>Ravindranath wrote:
</tt><blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><pre style="margin: 0em;">dave,</pre><br>
<pre style="margin: 0em;">For example   i have the following  configuration in  xdc file</pre><br>
<pre style="margin: 0em;">config  UInt32 ARR_SIZE = 2;</pre><br>
<pre style="margin: 0em;">instance:</pre><br>
<tt>config UInt32 myArr[ARR_SIZE ]= [0,0] /* here normal procedure is to 
initialize all the 2 elements. Suppose if ARR_SIZE is changed  to a 
higher value through the cfg file static initialization of myArr gives 
error. To avoid this static initialization of myArr needs  to be done 
some how  either in xs file  or some other place.</tt><br>
<br>
<tt>why we  need this type of declaration is application users  does not 
like to have pointers to which they have to declare variables and  
assign them to pointers in Params.</tt><br>
<br>
<pre style="margin: 0em;">Regards,
Ravindranath Andela</pre><br>
</blockquote><br>
]]></content:encoded>
		<pubDate>Thu, 27 Aug 2009 17:33:57 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00242.html</guid>
		<author>d-russo@xxxxxxx (dave russo)</author>
	</item>
	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Issue with declaring structure	variable and array under instance label in xdc fi</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00241.html</link>
		<description>dave, For example i have the following configuration in xdc file config UInt32 ARR_SIZE = 2; instance: config UInt32 myArr[ARR_SIZE ]= [0,0] /* here normal procedure is to initialize all the 2 elements. Suppose if ARR_SIZE is changed to a higher value thro...</description>
		<content:encoded><![CDATA[<pre style="margin: 0em;">dave,</pre><br>
<pre style="margin: 0em;">For example   i have the following  configuration in  xdc file</pre><br>
<pre style="margin: 0em;">config  UInt32 ARR_SIZE = 2;</pre><br>
<pre style="margin: 0em;">instance:</pre><br>
<tt>config UInt32 myArr[ARR_SIZE ]= [0,0] /* here normal procedure is to 
initialize all the 2 elements. Suppose if ARR_SIZE is changed  to a higher 
value through the cfg file static initialization of myArr gives error. To 
avoid this static initialization of myArr needs  to be done some how  
either in xs file  or some other place.</tt><br>
<br>
<tt>why we  need this type of declaration is application users  does not like 
to have pointers to which they have to declare variables and  assign them 
to pointers in Params.</tt><br>
<br>
<pre style="margin: 0em;">Regards,
Ravindranath Andela</pre><br>
<br>
]]></content:encoded>
		<pubDate>Thu, 27 Aug 2009 07:21:09 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00241.html</guid>
		<author>ravindranath.a@xxxxxxx (Ravindranath )</author>
	</item>


	<item>
		<title>[news.eclipse.dsdp.rtsc] Re: Issue with declaring structure variable and array under instance label in xdc fi</title>
		<link>http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00240.html</link>
		<description> </description>
		<content:encoded><![CDATA[<tt>Do you need the instance state to contain a config time 
generated/initialized array whose length is settable during 
configuration?  If so, you don't need to modify the params structure.</tt><br>
<br>
<tt>Static arrays can be created (and placed) via Memory.staticPlace() when 
you create static instances; see 
<a  href="http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/runtime/Memory.html#static.Place">http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/runtime/Memory.html#static.Place</a>.</tt><br>
<br>
<tt>An example of it's usage is the HeapMin module in the xdc.runtime 
package; see HeapMin.xdc and HeapMin.xs.</tt><br>
<br>
<tt>Can you describe a bit more about what you are trying to do?  It would 
make it easier to help craft an appropriate solution.</tt><br>
<br>
<tt>Ravindranath wrote:
</tt><blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><tt>my requirement is such that dimension of the array needs to be set 
thorough the cfg file. And in xdc/xs file  array elements should be 
initialized.</tt><br>
<br>
<pre style="margin: 0em;">Regards,
Ravindranath Andela</pre><br>
<pre style="margin: 0em;"><br></pre><br>
<pre style="margin: 0em;"><br></pre><br>
</blockquote><br>
]]></content:encoded>
		<pubDate>Wed, 26 Aug 2009 21:01:28 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.dsdp.rtsc/msg00240.html</guid>
		<author>d-russo@xxxxxxx (dave russo)</author>
	</item>

 
	</channel>
	</rss>
<!-- MHonArc v2.6.10 -->
