one way to see what's really going on is to look at the generated C code
that ultimately gets compiled into the final binary. The savec option
tells the compiler to keep the intermediate files in a directory for your
inspection:
chpl -o /tmp/out --*savec*=out test.chpl
On Thu, Jul 2, 2015 at 7:48 AM, Hui Zhang <[email protected]> wrote:
> Hello,
>
> Could anyone shed some light on how for loop is realized in Chapel with
> details ?
>
> As simple as "for i in 1..100", I feel it's calling some inner functions
> that are hidden from users, which consumes a lot running time, but I
> haven't had a clear clue yet...so any ideas how that happened ?
>
> Thanks
>
> --
> Best regards
>
>
> Hui Zhang
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Chapel-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chapel-developers
>
>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
