EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: R3.14.8 testing
From: "Ernest L. Williams Jr." <[email protected]>
To: Marty Kraimer <[email protected]>
Cc: Jeff Hill <[email protected]>, [email protected]
Date: Tue, 01 Nov 2005 17:20:11 -0500
On Tue, 2005-11-01 at 13:26 -0600, Marty Kraimer wrote:
> I did a cvs update and rebuild.
> exampleApp still crashes.
> 
> There are still lots of warning messages like
> 
> /fdmgr/fdmgr.cpp
> "../../../src/libCom/fdmgr/fdManager.h", line 171: Warning: Conversion 
> of 64 bit type value to "const unsigned" causes truncation.
> "../../../src/libCom/fdmgr/fdManager.h", line 171: Warning: Conversion 
> of 64 bit type value to "const unsigned" causes truncation.
> "../../../src/libCom/fdmgr/fdmgr.cpp", line 33: Warning: Conversion of 
> 64 bit type value to "const unsigned" causes truncation.
> 
> 
> I think we should create 3.14.8 and take care of this later.
> I am concerned that fixing the 64 bit problems will in turn cause new bugs.
Marty, I am not seeing this issue on linux AMD64. Is this happening on
Solaris 64-bit?


==============================================================================
[williams@ics-srv-epics1 iocamd64]$ ./st.cmd
#!../../bin/linux-x86_64/amd64
## You may have to change amd64 to something else
## everywhere it appears in this file
< envPaths
epicsEnvSet(ARCH,"linux-x86_64")
epicsEnvSet(IOC,"iocamd64")
epicsEnvSet(TOP,"/ade/epics/iocTop/R3.14.8/test")
epicsEnvSet(EPICS_BASE,"/ade/epics/supTop/base/R3.14.8")
cd /ade/epics/iocTop/R3.14.8/test
## Register all support components
dbLoadDatabase("dbd/amd64.dbd")
amd64_registerRecordDeviceDriver(pdbbase)
## Load record instances
dbLoadRecords("db/dbExample1.db","user=williamsHost")
dbLoadRecords("db/dbExample2.db","user=williamsHost,no=1,scan=1 second")
dbLoadRecords("db/dbExample2.db","user=williamsHost,no=2,scan=2 second")
dbLoadRecords("db/dbExample2.db","user=williamsHost,no=3,scan=5 second")
dbLoadRecords("db/dbSubExample.db","user=williamsHost")
## Set this to see messages from mySub
#var mySubDebug 1
cd /ade/epics/iocTop/R3.14.8/test/iocBoot/iocamd64
iocInit()
Starting iocInit
############################################################################
###  EPICS IOC CORE built on Oct 31 2005
###  EPICS R3.14.7 $$Name: R3-14-2_branch $$ $$Date: 2004/12/06 22:31:52
$$
############################################################################
iocInit: All initialization complete
## Start any sequence programs
#seq sncExample,"user=williamsHost"
online notify: beacon sock UDP read shutdown error was Transport
endpoint is not connected
epics> dbl
williamsHost:aiExample
williamsHost:aiExample1
williamsHost:aiExample2
williamsHost:aiExample3
williamsHost:calcExample
williamsHost:calcExample1
williamsHost:calcExample2
williamsHost:calcExample3
williamsHost:compressExample
williamsHost:subExample
williamsHost:xxxExample
epics>
======================================================================


Thanks,
Ernest








> 
> Marty
> 
> 
> Jeff Hill wrote:
> 
> >>I get many many warning messages like:
> >>
> >>"../../../include/epicsTime.h", line 328: Warning: Conversion of 64 bit
> >>type value to "unsigned" causes truncation.
> >>    
> >>
> >
> >This is because the epicsTime has a 64 bit unsigned seconds field and the
> >network time stamp has a 32 bit unsigned seconds' field. I committed a fix
> >(which just suppresses the warning allowing truncation by design to
> >continue). Here is the comment in the source code.
> >
> >    // epicsTime::secPastEpoch is based on ulong and has much greater range 
> >    // on 64 bit hosts than the orginal epicsTimeStamp::secPastEpoch. The 
> >    // epicsTimeStamp::secPastEpoch is based on epicsUInt32 so that it will 
> >    // match the original network protocol. Of course one can anticipate
> >    // that eventually, a epicsUInt64 based network time stamp will be 
> >    // introduced when 64 bit architectures are more ubiquitous.
> >    //
> >    // Truncation usually works fine here because the routines in this code
> >    // that compute time stamp differences and compare time stamps produce
> >    // good results when the operands are on either side of a time stamp
> >    // rollover as long as the difference between the operands does 
> >    // not exceed 1/2 of full range.
> >
> >
> >  
> >
> 


Replies:
Re: R3.14.8 testing Marty Kraimer
References:
RE: R3.14.8 testing Jeff Hill
Re: R3.14.8 testing Marty Kraimer

Navigate by Date:
Prev: Re: R3.14.8 testing Marty Kraimer
Next: Re: R3.14.8 testing Marty Kraimer
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: R3.14.8 testing Marty Kraimer
Next: Re: R3.14.8 testing Marty Kraimer
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·