Subject: |
[Bug 608956] Re: vxWorks 6.8 deprecates the use of taskVarLib |
From: |
mdavidsaver via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 17 Jun 2019 04:31:32 -0000 |
Have the past 9 years yielded any clarify on support for '__thread'? I
believe vxworks is the only blocker to use of '__thread', aka.
'__declspec(thread)' aka. 'thread_local'.
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/608956
Title:
vxWorks 6.8 deprecates the use of taskVarLib
Status in EPICS Base:
Triaged
Bug description:
The release notes say the taskVarLib facilities will be removed in a
future release, and they don't work on SMP systems anyway.
The __thread storage class replaces taskVarLib. It's not clear if any
vxWorks releases before 6.8 support __thread variables though.
Someone will have to modify src/libCom/osi/os/vxWorks/osdThread.c to
comply with this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/608956/+subscriptions
- Navigate by Date:
- Prev:
Re: epicsThreadSleep and epicsThreadSleepQuantum Konrad, Martin via Core-talk
- Next:
[Bug 1833108] [NEW] CA context not set during disconnect callback mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Jenkins build is back to normal : 3.15-normativeTypes-win64s #128 APS Jenkins via Core-talk
- Next:
[Bug 608956] Re: vxWorks 6.8 deprecates the use of taskVarLib Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|