> Apparently it no longer works. It segfaults for me on cases that used to > work with it. It was supposed to skip the module initialization phase > for possibly all modules (or at least the internal ones). All the modules > are still compiled - it's just that they are not run at program startup.
I see, OK. So it simplifies the execution-time initialization but not the compile-time issue (which is what I was aiming to simplify in this proposal). > Tests that used to work this way (and that I would expect minimal-modules > to compile) are in test/nostdlib. Huh... So these tests aren't breaking that I know of... Oh, but maybe they don't throw the --ignore-internal-modules flag via a COMPOPTS file either? > Anyway, all that means that the --ignore-internal-modules flag should > probably be removed and replaced by a minimal-modules compilation mode. OK, thanks. -Brad ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
