-----Original Message-----
From: Ernest L. Williams Jr. [mailto:[email protected]]
Sent: Wednesday, December 09, 2009 12:46 PM
To: Jeff Hill
Cc: 'Andrew Johnson'; 'Yves Lussignol'; [email protected]; 'Jean-
Francois Gournay'; [email protected]; 'Eric Bjorklund'; Ernest L.
Williams Jr.
Subject: Re: Any News on EPICS 3.14.11 with vxWorks 6.7
Jeff Hill wrote:
Hi Ernest,
Executive summary:
1) Apparently, GCC doesn’t fail with the MVME550 but this is very
similar
processor. What -mcpu flag was used with the MVME5500?
Not sure, if they have a separate CONFIG file for MVME5500
What we have with the distribution of BASE from APS is the following:
<>/configure/os/CONFIG.Common.vxWorks-ppc604
The flag is :
ARCH_DEP_CFLAGS_4 = -mcpu=604 -mstrict-align -fno-implicit-fp
2) I will need to try to reproduce it here with our vxWorks 6.6. That
will
require installation of EPICS R3.14.11 onto a new host here.
Okay, be sure to use the latest GNU Compiler patches from Windriver:
3) I wonder if -mcpu=604e or -mcpu=7450 would a closer match to the
board;
perhaps that’s worth a try.
I tried both options; still does not work. Fails the same way.
Sorry about the delay responding, Los Alamos was, for all practical
purposes, in stasis yesterday due to snow, wind, and power outages (I
spent
most of the day shoveling out three driveways).
A quick review of the current situation is in order. There was a no-
altivec
flag for the C++ compiler that might have helped, but it didn’t, and now
we
see that the issue does not occur with the MVME5500 but does occur with
the
MVME6600. The MVME5500 has an MPC7455 processor chip and the MVME6100
has an
MPC7457 processor chip. We are using -mcpu=604 when the compiler fails,
and
I am not sure what -mcpu option was used for the MVME5500 when it did
compile. Perhaps -mcpu=604e or -mcpu=7450 would be worth trying?
Again, I tried the different mcpu flags that you recommended. Still no
change; build fails.
By the way build for PPC603 architecture builds just fine. :)
I am only having a problem with PPC604
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC7457
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC7455
I don’t claim to have read up on the subtle differences between these
chips.
Nevertheless, the compiler should produce object code for the supported
CPU
architecture that we select so we have a compiler bug; we are just
looking
for a workaround when selecting different architectures.
I need some work-around in the cas source code; I definitely need this
because of the PV Gateway dependencies.
I _have_ tried to reproduce this in a small code but this is time
consuming
because we have been using Ernest's compiler to test. I will need to try
to
reproduce it here.
Jeff
______________________________________________________
Jeffrey O. Hill Email [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA FAX 505 665 5107
Message content: TSPA
-----Original Message-----
From: Ernest L. Williams Jr. [mailto:[email protected]]
Sent: Tuesday, December 08, 2009 10:27 AM
To: Jeff Hill
Cc: Andrew Johnson; Yves Lussignol; [email protected]; Jean-
Francois
Gournay; [email protected]; Ernest L. Williams Jr.
Subject: Any News on EPICS 3.14.11 with vxWorks 6.7
Hi Jeff,
Just wanted to follow up on the issue with vxWorks GNU compiler:
I don't understand why our colleagues don't see this problem?
/afs/slac/package/vxworks/devel/6.7/gnu/4.1.2-vxworks-6.7/x86-
linux2/bin/ccppc
-c -DCPU=PPC604 -DvxWorks -DBSD=44 -g -Wall
-mcpu=604 -mstrict-align -fno-implicit-fp -mlongcall -fno-builtin
-DBSD=44 -I. -I../O.Common -I. -I.. -I../../../../src/cas/generic
-I../../../../src/cas/io/bsdSocket -I../../../../src/cas/generic/st
-I../../../../src/cas/../ca -I../../../../include/os/vxWorks
-I../../../../include
-I/afs/slac/package/vxworks/devel/6.7/vxworks-6.7/target/h
-I/afs/slac/package/vxworks/devel/6.7/vxworks-6.7/target/h/wrn/coreip
../../../../src/cas/generic/st/casStreamOS.cc
In file included from
/afs/slac/package/vxworks/devel/6.7/vxworks-6.7/target/h/taskLib.h:257,
from
/afs/slac/package/vxworks/devel/6.7/vxworks-
6.7/target/h/private/selectLibP.h:24,
from
/afs/slac/package/vxworks/devel/6.7/vxworks-
6.7/target/h/selectLib.h:75,
from ../../../../include/os/vxWorks/osdSock.h:35,
from ../../../../include/osiSock.h:21,
from ../../../../include/fdManager.h:28,
from ../../../../src/cas/generic/st/casStreamOS.cc:18:
/afs/slac/package/vxworks/devel/6.7/vxworks-
6.7/target/h/vsbConfig.h:42:2:
warning: #warning "VxWorks Source Build (VSB) project not specified;
using default VxWorks UP configuration under
$WIND_BASE/target/lib/h/config"
../../../../src/cas/generic/st/casStreamOS.cc: In member function
'virtual epicsTimerNotify::expireStatus casStreamIOWakeup::expire(const
epicsTime&)':
../../../../src/cas/generic/st/casStreamOS.cc:283: error: unable to
find
a register to spill in class 'FLOAT_REGS'
../../../../src/cas/generic/st/casStreamOS.cc:283: error: this is the
insn:
(insn 162 161 163 9 ../../../../src/cas/generic/st/casStreamOS.cc:280
(set (reg:DF 119 [ D.21342 ])
(mem/s/c:DF (plus:SI (reg/f:SI 113 sfp)
(const_int 24 [0x18])) [0 D.21330+0 S8 A64])) 301
{*movdf_hardfloat32} (nil)
(nil))
../../../../src/cas/generic/st/casStreamOS.cc:283: confused by earlier
errors, bailing out
make[4]: *** [casStreamOS.o] Error 1
make[4]: Leaving directory
`/afs/slac.stanford.edu/g/lcls/vol8/epics/base/base-R3-14-
11/src/cas/build/O.vxWorks-ppc604_long'
make[3]: *** [install.vxWorks-ppc604_long] Error 2
make[3]: Leaving directory
`/afs/slac.stanford.edu/g/lcls/vol8/epics/base/base-R3-14-
11/src/cas/build'
make[2]: *** [build.install] Error 2
make[2]: Leaving directory
`/afs/slac.stanford.edu/g/lcls/vol8/epics/base/base-R3-14-11/src/cas'
make[1]: *** [cas.install] Error 2
make[1]: Leaving directory
`/afs/slac.stanford.edu/g/lcls/vol8/epics/base/base-R3-14-11/src'
Thanks,
Ernest
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·