View Issue Details

IDProjectCategoryView StatusLast Update
00017821003.1(2016/18)/Issue7+TC2Rationalepublic2024-06-11 09:07
Reporterdannyniu Assigned To 
PrioritynormalSeverityObjectionTypeEnhancement Request
Status ClosedResolutionAccepted As Marked 
NameDannyNiu/NJF
Organization<individual>
User Referencec181.pdf
SectionB.2.8 Realtime >> Rationale Relating to Timeouts
Page Number3628
Line Number123791
Interp Status---
Final Accepted Text0001782:0006564
Summary0001782: Standardize "pthread_yield"? Or change the example code?
DescriptionIn the example code at page 3628, the example used the `pthread_yield()` function.

This function is a common-place extension in most Pthread implementations, however, it was not included in the normative text of the current standard. Instead, `sched_yield()` is specified and included in the base.

C11 has the `thrd_yield()` function, which is part of the "threads.h" header.
Desired ActionStandardize `pthread_yield()` (as C11 has standardized `thrd_yield()`)
OR
replace the call in the code example with `sched_yield()`
OR
some other more preferrable solution?
Tagsapplied_after_i8d3, tc3-2008

Activities

geoffclare

2023-11-02 15:31

manager   bugnote:0006564

Change:
pthread_yield();
to:
sched_yield();

The editor may also change the brace indentation to match other parts of the standard. (lines 123780-123794 and lines 123804-123847).

Issue History

Date Modified Username Field Change
2023-10-17 11:30 dannyniu New Issue
2023-10-17 11:30 dannyniu Name => DannyNiu/NJF
2023-10-17 11:30 dannyniu Organization => <individual>
2023-10-17 11:30 dannyniu User Reference => c181.pdf
2023-10-17 11:30 dannyniu Section => B.2.8 Realtime >> Rationale Relating to Timeouts
2023-10-17 11:30 dannyniu Page Number => 3628
2023-10-17 11:30 dannyniu Line Number => 123791
2023-11-02 15:31 geoffclare Note Added: 0006564
2023-11-02 15:32 geoffclare Interp Status => ---
2023-11-02 15:32 geoffclare Final Accepted Text => 0000745:0001782
2023-11-02 15:32 geoffclare Status New => Resolved
2023-11-02 15:32 geoffclare Resolution Open => Accepted As Marked
2023-11-02 15:32 geoffclare Final Accepted Text 0000745:0001782 => 0001782:0006564
2023-11-02 15:33 geoffclare Tag Attached: tc3-2008
2023-11-14 10:44 geoffclare Status Resolved => Applied
2023-11-14 10:44 geoffclare Tag Attached: applied_after_i8d3
2024-06-11 09:07 agadmin Status Applied => Closed