From: hainque@news.enst.fr (Olivier Hainque)
Subject: Invalid asm statement with GNAT - Help !
Date: 1996/08/06
Date: 1996-08-06T00:00:00+00:00 [thread overview]
Message-ID: <4u7mdh$gvm@enst.enst.fr> (raw)
Hello all,
I am trying to port the GNAT runtime for an embedded OS running on
a 68302.
I configured gcc as a cross compiler for C and Ada and have troubles
while building a dummy runtime for my target :
$ make CC=gcc CFLAGS="-m68302 -msoft-float" gnatlib
... Everything runs fine for the first files, but ...
../../xgcc -B../../ -c -m68302 -msoft-float -O2 -gnatpg -I.
-I../../gcc-2.7.2/ada a-calcon.adb
leads to the following :
/var/tmp/cca002bf.s: Assembler messages:
/var/tmp/cca002bf.s:9: Error: invalid instruction for this architecture;
needs fpu (68040, 68060 or 68881/68882) -- statement `fmovem #0xfc,sp@-'
ignored
xgcc: Internal compiler error: program as got fatal signal 10
:-(
Of course, the runtime is not ported yet, so I don't expect it to be
completely operational at this time. However, I do not understand how the
compilation of an ada file, having specified special options, could lead
to an assembly file still containing unsupported statements for the given
target.
I have no such problem with the whole set of C files involved in the
construction of the embedded OS, and a "file *.o" on the first Ada
compiled objects gives "old sun-2 executable not stripped" which seems
nice. Without the -mxxx options, I get "mc68020 executable ..." which
are clearly not supported by the target, but which show that the options
I give do have an effect somewhere :-).
Any help would be greatly appreciated.
Thanks in advance.
Olivier
--
E-mail: hainque@email.enst.fr || Olivier.Hainque@enst.fr
P-mail: Telecom Paris
46, rue Barrault - 75634 Paris cedex 13
next reply other threads:[~1996-08-06 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-06 0:00 Olivier Hainque [this message]
1996-08-12 0:00 ` Invalid asm statement with GNAT - Help ! Olivier Cremel
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox