Marco,
     Thanks for replying back.  I have been to the website and read 
through portions of it (no, not the entire thing, line for line starting 
at the top, but selected portions starting with the first few sections 
and then 13 - Merge).  I had found those examples previously and was 
modeling my attempts on those.  Sorry, I disagree about the extensivity 
(yeah, making up words) of the documentation and the quality of examples 
or explanations.  Perhaps if you were already well versed in the 
underlying mechanics of the process and knew what you were doing, but 
not to an inexperienced novice such as myself.  My opinion, of course.  :)

But I went through it again and still was having no luck.  I don't 
recall exactly what problems I was having before (may have been the same 
as this time around), but here is what I ran into this time.  The 
primary issue is that I can't seem to find my merged file!  :)

Here is what I have for output (with -verbose on and an LS afterward):


$ cilly --verbose --save-temps --merge --keepmerged unitTests_jjc.c 
rngs.c dominion.c -o dominion-merged
Preprocessing unitTests_jjc.c
gcc -D_GNUCC -E -DCIL=1 unitTests_jjc.c -o ./unitTests_jjc.i
Saving source ./unitTests_jjc.i into ./unitTests_jjc.o
Preprocessing rngs.c
gcc -D_GNUCC -E -DCIL=1 rngs.c -o ./rngs.i
Saving source ./rngs.i into ./rngs.o
Preprocessing dominion.c
gcc -D_GNUCC -E -DCIL=1 dominion.c -o ./dominion.i
Saving source ./dominion.i into ./dominion.o
Merging saved sources into dominion-merged_comb.o (in process of linking 
dominion-merged)
Will merge the following: KeptFile=HASH(0x22cd378) 
KeptFile=HASH(0x22cfcf8) KeptFile=HASH(0x22cfe30)
Will just link the genuine object files:
After merge compile flags:
/home/joel/apps/crest/cil/obj/x86_LINUX/cilly.asm.exe --out 
./dominion-merged.cil.c --verbose ./unitTests_jjc.o ./rngs.o 
./dominion.o --mergedout ./dominion-merged_comb.c

$ ls
bin              dominion.h   interface.h             Makefile         
player.c  rngs.o           unitTests_jjc.o
cardDefs.h       dominion.i   Lin_Dominion_jc.cbp     moreFunctions.h  
rngs.c    rt.c
dominion.c       dominion.o   Lin_Dominion_jc.depend  obj              
rngs.h    unitTests_jjc.c
dominion.c.save  interface.c  Lin_Dominion_jc.layout  playdom.c        
rngs.i    unitTests_jjc.i



You can see that there is no ".comb.c" file.  The various .o and .i 
files are there, though (the result of the --save-temps flag I 
believe...I wasn't even seeing those before I found that flag).

The 'coming soon' statement is from the README file.


Thanks,
J



On 02/17/2011 01:12 AM, Marco Trudel wrote:
> Hey J
>
> On 16.02.2011 18:55, Justin wrote:
>> Hello all.  I am very new at using CIL, as probably obviated by my
>> question...
> Then you might want to read through http://hal.cs.berkeley.edu/cil/
>
>> I am trying to merge files into one, so that I can do some analysis on
>> it (using CREST).  I have two .c files and 3 .h files.  I can't seem to
>> figure out how to get CIL to merge these correctly.
> What did you try? How did it fail?
>
>>   The documentation talks about 'more info coming soon'.
> The documentation seems to be pretty extensive to me:
> http://hal.cs.berkeley.edu/cil/cil007.html
> Where does it say "more info coming soon"?
>>   The output needs to be .c format;
> I'd suggest to read through the website. All you need is there with very
> good examples and explanations.
>
>
> Hope that helps
> Marco
>
>> CREST has a script that runs on a .c file in order to implement it's
>> features.
>>
>> Thanks,
>> J

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
CIL-users mailing list
CIL-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cil-users

Reply via email to