| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1173.1 | | DIVING::DAVIS | Buckle Up, TED!, -- VMS Partner, DTN: 341-5342 | Thu Mar 16 1995 15:52 | 597 |
| 1173.2 | follow up.. | DIVING::DAVIS | Buckle Up, TED!, -- VMS Partner, DTN: 341-5342 | Thu Mar 16 1995 15:56 | 8 |
| 1173.3 | Looks like a known problem | DECC::VOGEL | | Thu Mar 16 1995 16:28 | 29 |
| 1173.4 | fixed in DECC T5.0 | DIVING::DAVIS | Buckle Up, TED!, -- VMS Partner, DTN: 341-5342 | Mon Mar 20 1995 15:26 | 4 |
| 1173.5 | Whats the downside to upgrading? | SYSTEM::HELLIAR | http://samedi.reo.dec.com/ | Tue Feb 04 1997 08:18 | 10 |
| We've hit this as well.
We currently have 4.0 on VAX/VMS and 4.1 in AXP/VMS. Is there any
downside to upgrading our compilers to 5.0 or above? E.g. will this
change any behaviour (apart from stopping crashes), or change the
pre-requisits of either the developement or target (run time) systems.
Regards,
Graham
|
| 1173.6 | upgrading much safer than standing pat | CAIRN::HARRIS | Kevin Harris, dtn 381-2039 | Tue Feb 04 1997 11:30 | 14 |
|
> We currently have 4.0 on VAX/VMS and 4.1 in AXP/VMS. Is there any
> downside to upgrading our compilers to 5.0 or above? E.g. will this
> change any behaviour (apart from stopping crashes), or change the
> pre-requisits of either the developement or target (run time) systems.
no and no
We recommend upgrading to the latest available DEC C kit. There are many
important bug fixes in each release that you should take advantage of. V4.0
was the first release of DEC C, and is now seriously obsolete. We don't claim
that each new release is totally free of new bugs, but the improvements outweigh
the regressions many times over.
-Kevin
|
| 1173.7 | Both V5.3 and V5.5 have been stable... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Feb 04 1997 11:40 | 23 |
|
: We currently have 4.0 on VAX/VMS and 4.1 in AXP/VMS. Is there any
: downside to upgrading our compilers to 5.0 or above? E.g. will this
: change any behaviour (apart from stopping crashes), or change the
: pre-requisits of either the developement or target (run time) systems.
There are a couple of bugs in the V5.5 compiler around compiling
modules that include specific include files (see previous reports),
but otherwise both V5.5 and V5.3 have been quite stable. (I've been
running both V5.3 and V5.5 compilers on various systems since shortly
after they each became available.)
I have noticed (and used) new support around 64-bit addressing, and
I've noticed better error messages, etc. I haven't seen any serious
problems -- save for the above-mentioned include bugs.
There are some changes around how DEC C uses the DECC$SHR RTL -- it's
now accessed by the compiler at run-time, so you'll need to issue a
/DEFINE for the target OpenVMS VMS version, and a DEFINE to get the
compiler to read the symbols from the target RTL. (There was a
discussion of this not too long ago... See 2071.*.)
You'll need to run your own tests locally, obviously...
|