Skip to Content.
Sympa Menu

charm - Re: [charm] [ppl] megatest fails for ibverbs and --with-production option (charm-6.4.0)

charm AT lists.siebelschool.illinois.edu

Subject: Charm++ parallel programming system

List archive

Re: [charm] [ppl] megatest fails for ibverbs and --with-production option (charm-6.4.0)


Chronological Thread 
  • From: Phil Miller <mille121 AT illinois.edu>
  • To: Gengbin Zheng <gzheng AT illinois.edu>, Thomas Albers <talbers AT binghamton.edu>
  • Cc: "charm AT cs.uiuc.edu" <charm AT cs.uiuc.edu>
  • Subject: Re: [charm] [ppl] megatest fails for ibverbs and --with-production option (charm-6.4.0)
  • Date: Fri, 30 Mar 2012 22:33:53 -0500
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/charm>
  • List-id: CHARM parallel programming system <charm.cs.uiuc.edu>

On Fri, Mar 30, 2012 at 21:09, Gengbin Zheng
<gzheng AT illinois.edu>
wrote:
> This looks like some issue with the Charm/Converse user-level threads.
>  I notice your gcc version is very new, I think we have not thoroughly
> tested against the latest version of gcc yet.

4.5 isn't that new - nearly 2 years. 4.6 has been out for about a year
now, and 4.7 was just released. I've tested successfully on both
pretty regularly.

> Can you try at link time, add:
>
>   -thread context
>
> and see if it makes difference.

Another possible fix, based on the failure you saw, is to build
Charm++ with -D_FORTIFY_SOURCE=0, like so:

./build charm++ net-linux-x86_64 ibverbs --with-production -D_FORTIFY_SOURCE=0

If this helps, we should probably add it directly to Charm++'s build
flags, since we're unlikely to ever want Fortify enabled.





Archive powered by MHonArc 2.6.16.

Top of Page