Subject: more leading underscores on mac68k
To: None <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 01/31/2002 09:09:08
To build an ELF kernel on mac68k with only 'option M68040' (not M68020
or M68030), I need the following. Does this look correct?
RCS file: /cvsroot/syssrc/sys/arch/mac68k/mac68k/locore.s,v
retrieving revision 1.136
diff -u -r1.136 locore.s
--- locore.s 2001/11/20 03:19:42 1.136
+++ locore.s 2002/01/31 14:48:41
@@ -458,7 +458,7 @@
#if !(defined(M68020) || defined(M68030))
- jra _badtrap
+ jra _C_LABEL(badtrap)
clrl %sp@- | stack adjust count
moveml #0xFFFF,%sp@- | save user registers
There are also two places in "locore.s" where both arguments to
ALTENTRY() have leading underscores. I'm a little confused about how
that's supposed to work. From inspecting <m68k/asm.h>, it looks to me as
if ALTENTRY() would add one too many underscores in the a.out case.
[There was one report to port-mac68k that profiling seems to be broken,
but the poster didn't say if he was building with PROF or GPROF or a.out
or ELF.] Is the right thing to do to just drop all the underscores?