Shortly, these 8 'deprecated' warnings were caused
by using functions purposely marked as deprecated.
Possibly they are planned for removing. More below.
The warning 'deprecated' occur for 2 files only:
1. modules/pvData/testApp/misc/testByteBuffer.cpp lines 164 and 191
testOk1(strncmp(buff->getArray(),&src[2],6)==0);
testOk1(strncmp(buf->getArray(),expect,6)==0);
- the warning is when the getArray() is invoked and used as
strncmp() arg (the warning place is the ')' of the getArray())
the buff/buf are of type ByteBuffer(32) #include <pv/byteBuffer.h>
- see modules/pvData/src/misc/pv/byteBuffer.h for the getArray() definition
EPICS_ALWAYS_INLINE const char* getArray() const EPICS_DEPRECATED
- modules/libcom/src/osi/compiler/clang/compilerSpecific.h
#define EPICS_DEPRECATED __attribute__((deprecated))
- obviously the warning is generated purposely
2. modules/pvAccess/testApp/remote/testServer.cpp lines 2261 2270 2279
epics::pvData::StructureConstPtr s =
getFieldCreate()->createFieldBuilder()->
=> addBoundedString("value", 8)->
add("timeStamp", getStandardField()->timeStamp())->
createStructure();
epics::pvData::StructureConstPtr s =
getFieldCreate()->createFieldBuilder()->
=> addBoundedArray("value", pvDouble, 8)->
add("timeStamp", getStandardField()->timeStamp())->
createStructure();
epics::pvData::StructureConstPtr s =
getFieldCreate()->createFieldBuilder()->
=> addFixedArray("value", pvDouble, 8)->
add("timeStamp", getStandardField()->timeStamp())->
createStructure();
the warning place is always on the ')'.
=> https://github.com/epics-base/pvDataCPP/issues/52
[-Wdeprecated-declarations]
- modules/pvData/src/pv/pvIntrospect.h
#define PVD_DEPRECATED_52 PVD_DEPRECATED(\
"See https://github.com/epics-base/pvDataCPP/issues/52")
- these functions addBoundedString(), addBoundedArray(),
and addFixedArray() are marked by the PVD_DEPRECATED_52
- modules/pvData/src/misc/pv/serialize.h
defines PVD_DEPRECATED(msg) if defined(PVD_INTERNAL)
(without the PVD_INTERNAL it is defined as do-nothing)
** Bug watch added: github.com/epics-base/pvDataCPP/issues #52
https://github.com/epics-base/pvDataCPP/issues/52
--
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/1905159
Title:
Fix warnings from recent compiler versions
Status in EPICS Base:
Triaged
Bug description:
Builds of EPICS Base using recent versions of gcc, clang and MSVC
generate compiler warnings, which we try to minimize if possible. Some
of these warnings can be prevented with suitable code modifications,
although the code must still build on the older compilers and other
architectures that we support.
Both the 3.15 and 7.0 branches can be examined for warnings; fixes
made on the 3.15 branch get propagated to the 7.0 branch during
periodic up-merges, so there is no need to make the same changes to
both branches. Some code only exists on one branch; for example the
gdd module was unbundled after 3.15, and there are many new modules in
7.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1905159/+subscriptions
- Navigate by Date:
- Prev:
[Bug 1932033] Re: base EPICS compilation misses convertRelease.pl Jerzy Tarasiuk via Core-talk
- Next:
[Bug 1905159] Re: Fix warnings from recent compiler versions Dirk Zimoch 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:
[Bug 1905159] Re: Fix warnings from recent compiler versions Jerzy Tarasiuk via Core-talk
- Next:
[Bug 1905159] Re: Fix warnings from recent compiler versions Dirk Zimoch 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
|