View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000287 | 1003.1(2004)/Issue 6 | System Interfaces | public | 2010-07-16 20:54 | 2017-01-05 10:32 |
Reporter | msbrown | Assigned To | ajosey | ||
Priority | normal | Severity | Objection | Type | Error |
Status | Closed | Resolution | Accepted As Marked | ||
Name | Mark Brown | ||||
Organization | The Open Group | ||||
User Reference | |||||
Section | nanosleep() | ||||
Page Number | na | ||||
Line Number | na | ||||
Interp Status | Approved | ||||
Final Accepted Text | 0000287:0000465 | ||||
Summary | 0000287: nanosleep behavior is unclear if rqtp==0 | ||||
Description | http://www.opengroup.org/onlinepubs/009695399/functions/nanosleep.html#tag_03_402 The behaviour of nanosleep is unclear if the rqtp parameter specifies a value of zero. If zero is specified, does nanosleep do nothing (ie. not suspend the current thread and return 0) or does it guarantee to suspend the thread for the minimum (sleep resolution) interval? [Copied from xshbug2.txt ERN 246. Originally submitted by pjardine. Processed too late to be included in IEEE Std 1003.1-2008. ] | ||||
Desired Action | Action: Provide clarification on the behaviour and return value of nanosleep() if rqtp specifies a value of zero. | ||||
Tags | No tags attached. |
|
Interpretation response ------------------------ The standard clearly states that it is specified to suspend for at least zero nanoseconds , and conforming implementations must conform to this. However, there is no guarantee that the thread will be suspended for any measurable interval. No conformance distinction can be made between implementations that return immediately versus those that return after a period of time. Rationale: ------------- See Description. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- None. |
|
Comments/objections on the proposed interpretation are due by COB Aug 31 2010 |
|
Closing this old bug as there does not appear to be any need for it to remain open. |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-07-16 20:54 | msbrown | New Issue | |
2010-07-16 20:54 | msbrown | Status | New => Under Review |
2010-07-16 20:54 | msbrown | Assigned To | => ajosey |
2010-07-16 20:54 | msbrown | Name | => Mark Brown |
2010-07-16 20:54 | msbrown | Organization | => The Open Group |
2010-07-16 20:54 | msbrown | Section | => nanosleep() |
2010-07-16 20:54 | msbrown | Page Number | => na |
2010-07-16 20:54 | msbrown | Line Number | => na |
2010-07-16 20:54 | msbrown | Interp Status | => Pending |
2010-07-16 20:54 | msbrown | Issue generated from: 0000286 | |
2010-07-16 20:59 | msbrown | Note Added: 0000465 | |
2010-07-16 20:59 | msbrown | Final Accepted Text | => 0000287:0000465 |
2010-07-16 20:59 | msbrown | Status | Under Review => Interpretation Required |
2010-07-16 20:59 | msbrown | Resolution | Open => Accepted As Marked |
2010-07-16 21:02 | msbrown | Issue cloned: 0000288 | |
2010-07-30 08:21 | ajosey | Interp Status | Pending => Proposed |
2010-07-30 08:21 | ajosey | Note Added: 0000503 | |
2010-09-03 16:43 | ajosey | Interp Status | Proposed => Approved |
2017-01-05 10:32 | geoffclare | Note Added: 0003531 | |
2017-01-05 10:32 | geoffclare | Status | Interpretation Required => Closed |