| Age | Commit message (Collapse) | Author |
|---|
|
The only code change observed is actually a case
where we were not doing that as needed:
00000000 <__GI_tzset>:
-53 push %ebx
-e8 00 00 00 00 call 6 <__GI_tzset+0x6>
-5b pop %ebx
-81 c3 03 00 00 00 add $0x3,%ebx
- R_386_GOTPC _GLOBAL_OFFSET_TABLE_
6a 00 push $0x0
-e8 fc ff ff ff call 10 <__GI_tzset+0x10>
- R_386_PLT32 time
+e8 fc ff ff ff call 3 <__GI_tzset+0x3>
+ R_386_PC32 __GI_time
3d ff 4e 98 45 cmp $0x45984eff,%eax
0f 9e c0 setle %al
0f b6 c0 movzbl %al,%eax
50 push %eax
-e8 fc ff ff ff call 21 <__GI_tzset+0x21>
+e8 fc ff ff ff call 14 <__GI_tzset+0x14>
R_386_PC32 _time_tzset
58 pop %eax
5a pop %edx
-5b pop %ebx
c3 ret
No mass migration of libc_hidden_proto(foo) planned.
Lets wait for potential fallout first.
|
|
The attached patch adds support for compiling arm uClibc as pure Thumb code.
This is needed because some recent ARM codes do not implement traditional ARM
mode. Specifically:
* Cortex-M1 - An extremely minimal FPGA based core that only implements
Thumb-1 (aka ARMv6-M).
* Cortex-M3 - A Thumb-2 only ARMv7-M core.
Most of uClibc already builds in Thumb mode, all that is left are a handful of
assembly bits.
Tested on arm-uclinuxeabi.
|
|
Add sysdeps/linux/$(TARGET_ARCH) to the list of includes. Needed by some of
the Blackfin specific string assembly files.
|
|
a problem where the linker was trying to use the wrong symbol name for the
init function.
Define SYMBOL_PREFIX as _ in Rules.mak for h8300, bfin, i960,
microblaze, and v850. Add -D__UCLIBC_UNDERSCORES__ in CFLAGS for targets
which define SYMBOL_PREFIX as _. Remove defines and undefs from
uClibc_arch_features.h of each target.
Add $(SYMBOL_PREFIX) to __uClibc_init when passed by ld option -init.
|
|
|
|
|
|
The following patches add support for the Xtensa processor architecture
to uClibc. They are based on a recent SVN checkout (12/05/2007).
The first patch (attached to this post) adds Xtensa support to various
shared configuration and make files. The following patches then include
the Xtensa specific files and directories.
I welcome any feedback and would appreciate it if you could include the
patches into the mainline tree. I am certainly committed to maintain the port.
Bob Wilson was kind enough to review the patches.
Some notes about the architecture: Xtensa is a configurable and
extensible processor architecture developed by Tensilica. For more
information, please visit: www.linux-xtensa.org.
|
|
transparent
|
|
|
|
<hcegtvedt@atmel.com>
|
|
|
|
|
|
|
|
- adjust setting flags accordingly to use (hardcoded, see below) -Wl,
Potential improvements:
*) --warn-unresolved-symbols should perhaps be used for all libs
*) eventually rename LDFLAGS to CC_LDFLAGS
*) probe for compiler driver's notion of flag to use for passing in
linker flags (i.e. don't hardcode "-Wl,")
|
|
|
|
GCC 4.3 will put fixed headers in a seperate include-fixed directory.
And I don't think that there are people who are still using the 'stupid'
GCC which cannot handle -iwithprefix, at least it works with gcc-3.3.x.
|
|
|
|
|
|
UCLIBC_FORMAT_SHARED_FLAT and -msep-data for UCLIBC_FORMAT_FLAT_SEP_DATA
|
|
|
|
versioning
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
clean up E500 math support somewhat.
From Steve Papacharalambous with mods by me.
|
|
in the powerpc arch code and make more code common with
classic PowerPC. From Steve Papacharalambous
Lets hope I didn't break something.
|
|
|
|
Math support to be done.
From Steve Papacharalambous, stevep@freescale.com
|
|
|
|
config option --enable-secureplt. The assembler must also
supports R_PPC_REL16* relocations. gcc 4.1.1 and binutils 2.17
is known to do this.
|
|
may need to update their paths slightly
|
|
|
|
|
|
libraries
|
|
|
|
Add selection of 3 ABI.
CPU_CFLAGS is needed to generate correct sysnum.h.
Fix test/Rules.mak.
|
|
|
|
|
|
at some point in the relatively near future.
|
|
I had clearly run search/replace on that were cluttering things up.
|
|
on i.e. NOSTRIP=n gets a bit confusing.
|
|
|
|
|
|
use trigraphs in uClibc, so if one exists, we should be cutting it out, not ignoring it
|
|
m68k is one of those targets that does not accept -fPIC across the board.
It is supported for 68020 and above, but not for 68000, 68010, or Coldfire,
where using -fPIC leads to a compiler error. (Note that the error is flagged
by cc1 proper, so it probably wouldn't have mattered with older compilers.
It only matters now because cc1 is used to preprocess assembly code.)
The attached patch makes m68k targets use -fpic instead of -fPIC.
|
|
|
