This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Definitely Getting Closer


Mark Palmerino wrote:
> 
> I still don't know why there are differences in the definitions of the
> vector*defaults, but apparently those differences aren't stopping the
> execution of this simple, simple program.

 Your 'rm_crt0.S' tells this:

------------------------ clip ------------------------------------------
	.globl	SYM(__vector_buserror_default)
SYM (__vector_buserror_default):

#if !defined (__mcf5200__) && !defined (__mcpu32__) && !defined (__mc68332__) \
 && !defined(__mc68010__) && !defined (__mc68020__) && !defined (__mc68030__) \
 && !defined (__mc68040__) && !defined (__mc68060__)
	ori	IMM(0x700),sr
	movel	sp@(10),d6
	moveql	IMM(2),d7
	bra	001b
#endif

	.globl	SYM(__vector_addrerror_default)
SYM (__vector_addrerror_default):

#if !defined (__mcf5200__) && !defined (__mcpu32__) && !defined (__mc68332__) \
 && !defined(__mc68010__) && !defined (__mc68020__) && !defined (__mc68030__) \
 && !defined (__mc68040__) && !defined (__mc68060__)
	ori	IMM(0x700),sr
	movel	sp@(10),d6
	moveql	IMM(3),d7
	bra	001b
#endif
------------------------ clip ------------------------------------------

 Just look at what '-Dm68xyz' options the compiler gives to the 'cpp' there and
you will see that the addresses being the same is right for m68332 !!! The DOS-
hosted compiler under Windoze produced m68000-code, not m68332-code...
 
> I guess the next question is, how can I discover why the libraries from the
> windows system are successful at producing a working program while the
> libraries that were built under unix are not successful?

 Perhaps there really is some problem with the mcpu32-support in gcc-2.8.1, just
remember that it was originally disabled ! The "Windows"-libs were compiled with
egcs-1.1.2, not with gcc-2.8.1 although the '2.8.1' was a ghost there...

> Again, I hardly know where to begin...

 What about building gcc-2.95.3-pre4 for m68k-coff now or later ? ;-) And adding
the ISR-patches I sent into the sources. The 2.95.3 should serve for a while...

Cheers, Kai


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]