SemanticsOfMorecore

PnkFelix is using this space to collect references to all the places where the millicode procedure mc_morecore is invoked, and determine what semantics it is supposed to have. (See Ticket #119.)

The reason he is doing this is that in his fix for Ticket #92, he put in a hack where mc_morecore would allocate a large amount of core as a conservative guess at what the requestor might want. But this was only to work around problems with the Intel backend (both NASM and IAssassin variants); it could be that the right solution would have been to call mc_alloc or mc_alloci with the actual parameter of how much storage to allocate.

(Note however that this hack, changeset:3104, should only have affected the stopcopy collector. This is revelant because PnkFelix had hypothesized over the weekend that the reason Sassy is retaining storage in an evil manner was because of changeset:3104; this hypothesis doesn't hold up when one considers that Sassy's misbehavior was being demonstrated on the standard collector.)

Lars introduced mc_morecore as a fix for bug 135 (under the old bug numbering scheme; see Ticket #97).

See:

• changeset:5605
• changeset:3104
• changeset:972, changeset:967, changeset:966, changeset:965, changeset:964, changeset:963