Hi - > >> OK. The old chapel-bugs list isn't being maintained right? > >That's right, we retired it in favor of GitHub issues in order to make >bugs more searchable, maintainable, and less inbox-oriented. > >> I just set it in case I need to use the llvm communication optimization >>as >> instructed, but it's not necessary for now. And yes, you are right. >>Afer I >> unset CHPL_WIDE_POINTERS environment variable, it works now. So, does it >> count a bug right now? :P > >I'm not sure... Michael?
If there is a bug, it's that we have CHPL_WIDE_POINTERS at all and/or that the documentation says to set it. It's a TODO of mine to get --llvm-wide-opt to work with the usual struct wide pointers and then to retire that environment variable. Unfortunately it has recently tripped up both Hui and one of our GSoC students. Right now, --llvm + CHPL_COMM is not even working, see issue #6149. -michael ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
