Project

General

Profile

Bug #1519

Entry methods with no parameters ignore priority from CkEntryOptions

Added by Phil Miller 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Charmxi
Target version:
Start date:
02/18/2016
Due date:
% Done:

100%


Description

We've fixed zero-argument entry methods to accept CkEntryOptions at the call site, and to respect group construction dependences, so their semantics are at least strictly correct. We're just missing priority/queueing stategy now, which is part of the performance semantics, but not the program correctness.

It's clear why it's implemented this way - the code on both send and receive sides would have to be duplicated to choose between working with a zero-payload system message and a dynamically allocated message with room for a priority or whatever else the options might dictate. Nevertheless, it's a somewhat glaring and surprising inconsistency that some entry methods can be passed options, and others can't.


Related issues

Copied from Charm++ - Bug #987: Entry methods with no parameters can't be called with CkEntryOptions, can't take group construction dependence. Merged 02/18/2016

History

#1 Updated by Phil Miller 3 months ago

  • Copied from Bug #987: Entry methods with no parameters can't be called with CkEntryOptions, can't take group construction dependence. added

Also available in: Atom PDF