than -0x20000000, not -0x1f000000. Quells the endless stream
of
ld: Double word displacement -535682276, out of range
style warnings that have annoyed my once too often.
things like the .note.netbsd.ident section are provided by crti/crtn.
crti/crtn also provide the _init() and _fini() routines.
crtbegin/crtend now only provide support for ctors/dtors. This paves
the way to using the "crtstuff" provided with GCC (when we upgrade to
GCC 3.3), which provides, among other things, much better C++/Java
exception handling.
macho_hdr, argc, *argv, NULL, *envp, NULL, progname, NULL,
*progname, **argv, **envp
Where progname is a pointer to the program name as given in the first
argument to execve(), and macho_hdr a pointer to the Mach-O header at
the beginning of the executable file.
* If -mhard-float is passed to the compiler, pass -mfpa10 to the assembler.
* If -msoft-float is passed to the compiler, pass -mfpu=softvfp to the
assembler.
* If neither -mhard-float nor -msoft-float are passed to the compiler,
pass -mfpu=softvfp to the assembler.
These changes properly mark objects as using soft-VFP, as is the default
code generation for NetBSD ARM ELF.
* FPU_MEMMULTI -- only include the FPU_FPA10 bit.
* FPU_ARCH_VFP -- define, meaning "uses VFP-format layout".
* FPU_FPA -- define short-hand for (FPU_CORE|FPU_FPA10).
* FPU_DEFAULT -- FPU_ALL -> FPU_FPA.
* Floating point instructions -- FPU_ALL -> FPU_FPA.
* Also set F_SOFT_FLOAT if FPU_ARCH_VFP.
* Set F_VFP_FLOAT if FPU_ARCH_VFP.
* md_atof: lay out bytes properly if using VFP.
* Accept -mfpu=softvfp.
* For -mall, set the FPU part of cpu_variant to FPU_FPA, instead of
FPU_ALL.
pdc202xx_setup_channel, pdc20268_setup_channel:
Properly compute the address of the DMA control register for channel 1.
I think the controllers ignore these bits, I suspect it's only there so that
the BIOS can tell the OS is has configured DMA, but better be correct.
Thanks to Alexander Yurchenko for pointing this out.
- c_gets() was usually returning a length, but sometimes
one of the CC_xxx values (which are small +ve integers)!
- fixed c_gets() by putting a ' ' under the cursor.
From David Laight.
C-referenceable names, i.e. "link sets") that happens with explicit
LMAs in the linker script:
* As orphans are sorted after sections, the effective
size of the section is changed. Record a size ajustment
for each orphan that is sorted after the section.
...and for sections which have an explicit load address expression:
* The first time an orphan is sorted after a section,
copy the load_base expression to the orphan, adding
the _unadjusted_ size of the parent section. We need
to use the unadjusted size because by the time the
expression can be folded, all of the orphan size
adjustments will have accumulated, resulting in misplacing
the orphan.
* For each subsequent orphan sorted after a section,
set the load_base of the orphan to the load address
of the previous orphan plus the size of the previous
orphan (actually, the unadjusted size, but for orphans,
size and unadjusted size are always equal).
