Charm++ parallel programming system

[Phil Miller <mille121 AT illinois.edu>]

It looks like you're working with generated .ci file code, and the translator is running out of memory. We could probably find ways to reduce its footprint, but the applicable use cases would make that fairly low priority. As a work-around, could you emit each generated module to a separate .ci file and run them through charmc individually?

On Tue, Jul 26, 2016 at 12:20 PM, Nels John Frazier <nfrazie1 AT uwyo.edu> wrote:

I'm working with charm 6.7.1 and ran across a bug in charmc/charmxi.

I have a .ci file with 458 modules in it, that look like this:

module par65800151
{
    PUPable par65800151;
}

When I have more than 334 of these modules in the .ci file, I get the following error when trying to compile:

charm/bin/charmc  ../generated_code/charm_diversions/parcels.ci
charm/bin/charmc: line 192: 14547 Segmentation fault      (core dumped) charm/bin/charmxi -orig-file ../generated_code/charm_diversions/parcels.ci
Fatal Error by charmc in directory management/build
   Command charm/bin/charmxi -orig-file ../generated_code/charm_diversions/parcels.ci returned error code 139
charmc exiting...

With 334 or less modules, it compiles fine.

Nels Frazier