liberty-eiffel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Liberty-eiffel] Bug #44601


From: Raphael Mack
Subject: Re: [Liberty-eiffel] Bug #44601
Date: Wed, 15 Jun 2016 21:56:50 +0200

Hi,

Am Mittwoch, den 15.06.2016, 09:32 -0400 schrieb Mehul Sanghvi:
> So I do the following:
> 
> 
>    cd target/bin/compile_to_c.d
>    ./compile_to_c -verbose -boost -no_gc compile_to_c -o
> compile_to_c.new
> 
> 
> And there is no compile_to_c.new binary generated.  I am guessing it
> should be in the same directory where
> I am running the command.  Or not ? 


compile_to_c just compiles to C, not to binary... there is a
compile_to_c.make file generated, which contains all the commands to
generate a binary from it.

grep -v '^#' compile_to_c.make | while read cmd ; do $cmd ; done

will do the trick.

Rapha
> 
> 
> 
> 
> cheers,
> 
> 
>       mehul
> 
> 
> 
> 
> 
> On Mon, Jun 13, 2016 at 10:16 PM, Mehul Sanghvi
> <address@hidden> wrote:
>         Yes that did the trick.   I was able to get a new germ which
>         has support for clang on OSX/Darwin/macOS.  
>         
>         
>         The problem I am running into now is that when I run
>         install.sh  I am not getting a "compile_to_c.new"  generated
>         but the following:
>         
>         
>             progress 30 1 $MAXTOOLCOUNT "T1: compile_to_c"
>             run ./compile_to_c -verbose -boost -no_gc compile_to_c -o
>         compile_to_c.new
>         
>         
>         I have tried running the command manually and it is no
>         different from when being run in the script.  
>         
>         
>         The below are results I see before the command completes:
>         
>         
>              Total Number of "inspect" used for Dynamic dispatch: 9129
>              Total Number of Merged "when" clauses (cumulated): 5097
>              Assignment graph: 659 nodes and 2012 transitions.
>              FEATURE_STAMPs total number = 5920
>              FEATURE_STAMPs with rename  = 39
>              Total time spent in parser: 00:00.705835
>              Total time spent getting started: 00:00.174095
>              Total time spent specializing one type: 00:14.933290
>              Total time spent specializing and checking: 00:11.650085
>              Total time spent collecting features: 00:00.695697
>              Total time spent inlining dynamic dispatch: 00:01.146237
>              Total time spent simplifying: 00:03.118921
>              Total time spent adapting features: 00:00.222636
>              Total time spent safety checking: 00:00.000058
>              Type-system safety check not performed in this mode
>              (use the -safety_check flag).
>              Done.
>              Writing "compile_to_c.id" file.
>              Aliased STRINGs: 58923.
>         
>         
>         
>         
>         The log file does not have anything that indicates any
>         issues.  
>         
>         
>         
>         
>         Thoughts, suggestions ? 
>         
>         
>         
>         
>         cheers,
>         
>         
>              mehul
>         
>         
>         
>         On Mon, Jun 13, 2016 at 2:49 PM, Raphael Mack
>         <address@hidden> wrote:
>                 Am Montag, den 13.06.2016, 10:11 -0400 schrieb Mehul
>                 Sanghvi:
>                 >
>                 > Yes that is true.
>                 >
>                 >
>                 > Let me re-compile that again.  I had run
>                 make-germ.sh and it had
>                 > deleted resources/smarteiffel-germ/*.c but nothing
>                 that a "git pull"
>                 > can not fix.
>                 >
>                 >
>                 > Any other options that I need to be using when
>                 compiling compile_2_c
>                 > and generating the germ with clang support ?
>                 
>                 -boost -no_gc
>                 
>                 should be sufficient. The interesting question is,
>                 whether we need
>                 special handling for clang or whether it is
>                 sufficiently compatible to
>                 gcc. - But you'll find out and, as the germ code
>                 already compiles it
>                 looks good in my eyes.
>                 
>                 Regards,
>                 Rapha
>                 
>                 
>         
>         
>         
>         
>         -- 
>         Mehul N. Sanghvi
>         email: address@hidden
> 
> 
> 
> 
> -- 
> Mehul N. Sanghvi
> email: address@hidden





reply via email to

[Prev in Thread] Current Thread [Next in Thread]