Analog Devices VISUALDSP++ 3.5 Manual page 528

Tools Differences
ELF/DWARF-2 format. As a result, AEXE-formatted files must be
recompiled or reassembled in order to be debugged under
VisualDSP++ 3.5. An ELF/DWARF-to-AEXE conversion utility is
available in VisualDSP++ 3.5 that will perform back-conversion.
An AEXE-to-ELF conversion utility performs forward conversion.
• Some assembly instructions and directives have changed from the
VisualDSP 6.1 syntax, but a
provided to assemble files in the old syntax. You may need to
review diagnostic messages and revise your source code in order to
reassemble your source. Legacy syntax and the new syntax under
VisualDSP++ 3.5 cannot be used together in the same source file.
They can be mixed together within the same project, as long as
they are assembled in different source files.
• Some C compiler extensions to the ISO/ANSI standard have
changed. If you use any of the modified or removed extensions,
you must revise your code in order to rebuild your project.
• The run-time model has changed. If you call a VisualDSP Release
6.1 assembly language subroutine from your C/C++ program, you
must revise the assembly code to comply with the new rules for the
C/C++ run-time environment.
• The Architecture File (
using your Release 6.1 object files or object libraries, you must cre-
ate a Linker Description File for each object or object library before
using the new Linker.
The remainder of this section describes these and other known differences
between VisualDSP Releases 6.1 and VisualDSP++ 3.5. It also provides
assistance when possible for making these required changes.
A-2
-legacy
) is no longer supported. If you re-link
.ACH
VisualDSP++ 3.5 C/C++ Compiler and Library Manual
assembler switch has been
for ADSP-219x DSPs