| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 480.1 | | DECCXL::OUELLETTE | crunch | Thu Mar 13 1997 12:46 | 13 |
| Not as such. You can use link -dump -disasm foo.exe to see the instructions.
It's pretty easy to spot unoptimized code... if you've ever read assembly
before. Code compiled for EV56 will have stb and stw instructions.
It takes an expert to tell the difference between code scheduled for
EV4 and EV5, but even that's possible.
At one time we were putting "what text" into object files, but given
that windows applications have thousands of files, those thousands of
strings were problematically large. For a time, a lighter weight soloution
using COMDAT strings and a pointer per file was kicked around, but due
to lack of demand, priority and people leaving digital, it never got done.
Roland.
|
| 480.2 | Compiler Switchable? | SWAM1::POIANI_MI | | Fri Mar 28 1997 10:06 | 4 |
| Is there a Vis C++ or DEC FORTRAN for Alpha NT compiler switch similar
to the UNIX "-tune ev5" switch to optimize for a given CPU?
MP
|
| 480.3 | | GEMEVN::GLOSSOP | Only the paranoid survive | Fri Mar 28 1997 10:17 | 7 |
| > Vis C++
-QA21164
> DEC FORTRAN
probably -tune ev5, but I'm not positive
|
| 480.4 | that's right | HYDRA::DONSBACH | Jeff Donsbach, Software Partner Engineering, DTN 297-6862 | Mon Mar 31 1997 21:39 | 8 |
|
.3 is correct. /QA21164 == -tune ev5
In VC++ 4.2 and later, there is also /QA21164A == -tune ev56,
though I don't think it's documented in the on-line manuals.
-Jeff D.
|
| 480.5 | Code faults | DECWET::METZGER | | Thu Apr 03 1997 11:07 | 16 |
| The way to find out where in the code the faults are occurring is to
disable fixups by running axpalign/enable, attach the debugger to the
process when an alignment fault is reported by the OS (i.e. press the
Cancel button from the dialog box informing that an alignment fault
has occured) and examine the call stack.
Information about porting code from Intel to RISC platforms comes as
part of the VC5.0 tutorials that ship with the RISC edition. Look under
"Developer Products\Visual C++\Visual C++ RISC programmer's guide". If
a piece of code is created with these guidelines in mind (which are not
many), then porting it to a RISC platform should be a matter of just
adding a RISC configuration to the project.
|