search for: __lshrdi3

Displaying 20 results from an estimated 35 matches for "__lshrdi3".

2019 Aug 15
2
Slow XCHG in arch/i386/libgcc/__ashrdi3.S and arch/i386/libgcc/__lshrdi3.S
Hi, both https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__ashldi3.S and https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__lshrdi3.S use the following code sequences for shift counts greater 31: 1: 1: xorl %edx,%edx shrl %cl,%edx shl %cl,%eax xorl %eax,%eax ^ xchgl %edx,%eax xchgl %edx,%eax ret ret At least and e...
2017 May 19
2
When a libcall will be generated?
Hi All, I am looking at a linker error under O2: undefined symbol __lshrdi3 I have two questions here: 1. Does that mean our libgcc (?) doesn't implement __lshrdi3? Or more generally, why I have such linker error? 2. Seems some operations are combined, and replaced with __lshrdi3 call. I am interested in when such libcall will be generated? Could you...
2019 Aug 19
0
Slow XCHG in arch/i386/libgcc/__ashrdi3.S and arch/i386/libgcc/__lshrdi3.S
On 8/14/19 9:42 PM, Stefan Kanthak wrote: > Hi, > > both > https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__ashldi3.S > and > https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__lshrdi3.S > use the following code sequences for shift counts greater 31: > > 1: 1: > xorl %edx,%edx shrl %cl,%edx > shl %cl,%eax xorl %eax,%eax > ^ > xchgl %edx,%eax xchgl %edx,%eax > ret...
2019 Aug 20
1
Slow XCHG in arch/i386/libgcc/__ashrdi3.S and arch/i386/libgcc/__lshrdi3.S
...: > On 8/14/19 9:42 PM, Stefan Kanthak wrote: >> Hi, >> >> both >> https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__ashldi3.S >> and >> https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__lshrdi3.S >> use the following code sequences for shift counts greater 31: >> >> 1: 1: >> xorl %edx,%edx shrl %cl,%edx >> shl %cl,%eax xorl %eax,%eax >> ^ >> xchgl %edx,%eax xchg...
2006 Oct 16
1
[LLVMdev] TargetExternalSymbol and TargetGlobalAddress
I have noticed that TargetGlobalAddress is generated for "source code" functions and TargetExternalSymbol is generated for builtins like __lshrdi3. What is the difference between TargetExternalSymbol and TargetGlobalAddress? Thanks, Rafael
2006 Jun 26
0
[klibc 24/43] i386 support for klibc
...h/i386/MCONFIG | 33 ++++++++ usr/klibc/arch/i386/Makefile.inc | 30 +++++++ usr/klibc/arch/i386/crt0.S | 31 +++++++ usr/klibc/arch/i386/libgcc/__ashldi3.S | 29 +++++++ usr/klibc/arch/i386/libgcc/__ashrdi3.S | 29 +++++++ usr/klibc/arch/i386/libgcc/__lshrdi3.S | 29 +++++++ usr/klibc/arch/i386/libgcc/__muldi3.S | 34 ++++++++ usr/klibc/arch/i386/libgcc/__negdi2.S | 21 +++++ usr/klibc/arch/i386/open.S | 29 +++++++ usr/klibc/arch/i386/openat.S | 26 ++++++ usr/klibc/arch/i386/setjmp.S | 58 +++++...
2014 Jun 09
3
How to use --once? Does it work?
> On 06/08/2014 02:58 PM, Ady wrote: > >> > >> To be clear, I am not saying there is no bug - there might be. > >> > > > > I performed the following test with several versions of Syslinux: > > > > 1_ Execute: > > 'extlinux --once=non_default_label --install /mnt/sda1' ; > > 2_ In first reboot, the
2014 Jun 09
4
How to use --once? Does it work?
...e > Info: Symbol dev_stdcon_w is defined more than once > Info: Symbol __moddi3 is defined more than once > Info: Symbol __syslinux_adv_ptr is defined more than once > Info: Symbol __negdi2 is defined more than once > Info: Symbol __umoddi3 is defined more than once > Info: Symbol __lshrdi3 is defined more than once > Info: Symbol __dtors_end is defined more than once > Info: Symbol __dtors_start is defined more than once > Info: Symbol dev_null_r is defined more than once > Info: Symbol __ashldi3 is defined more than once > Info: Symbol __udivdi3 is defined more than o...
2008 Jun 05
1
[LLVMdev] lli/JIT missing libgcc symbols on Mingw32/x86
...di3); + EXPLICIT_SYMBOL_DEF(__eprintf); + EXPLICIT_SYMBOL_DEF(__fixdfdi); + EXPLICIT_SYMBOL_DEF(__fixsfdi); + EXPLICIT_SYMBOL_DEF(__fixunsdfdi); + EXPLICIT_SYMBOL_DEF(__fixunssfdi); + EXPLICIT_SYMBOL_DEF(__floatdidf); + EXPLICIT_SYMBOL_DEF(__floatdisf); + EXPLICIT_SYMBOL_DEF(__lshrdi3); + EXPLICIT_SYMBOL_DEF(__moddi3); + EXPLICIT_SYMBOL_DEF(__udivdi3); + EXPLICIT_SYMBOL_DEF(__umoddi3); #elif defined(_MSC_VER) EXPLICIT_SYMBOL_DEF(_alloca_probe); #endif @@ -157,6 +172,21 @@ { EXPLICIT_SYMBOL(_alloca); EXPLICIT_SYMBOL(__main); + EXPLICIT_SYMBOL(_...
2010 Feb 02
2
[LLVMdev] __fixunsdfdi and etc with Visual Studio JIT?
Hello > The bitcode was generated by llvm-gcc v2.6 for Mingw32/x86, which is > available for download at the llvm site. > Please let me know, if i should tell more. Well, the answer is pretty obvious then. These calls are not generated by JIT. They are already in your bitcode - they are generated by llvm-gcc. The purpose of these calls were alreade explained by Eli. You should either
2015 Mar 06
0
[klibc:master] add-mips64-support-arch-mips32
...r/klibc/arch/mips64/Kbuild +++ b/usr/klibc/arch/mips64/Kbuild @@ -1,3 +1,14 @@ # # klibc files for mips64 # + +klib-y := ../mips/pipe.o ../mips/vfork.o setjmp.o ../mips/syscall.o + +klib-y += ../../libgcc/__clzsi2.o ../../libgcc/__ashldi3.o +klib-y += ../../libgcc/__ashrdi3.o ../../libgcc/__lshrdi3.o +klib-y += ../../libgcc/__divdi3.o ../../libgcc/__moddi3.o +klib-y += ../../libgcc/__udivdi3.o ../../libgcc/__umoddi3.o +klib-y += ../../libgcc/__udivmoddi4.o + +always := crt0.o +targets := crt0.o diff --git a/usr/klibc/arch/mips/sysstub.ph b/usr/klibc/arch/mips64/sysstub.ph similarity i...
2014 Jun 09
0
How to use --once? Does it work?
...hrdi3 is defined more than once Info: Symbol dev_stdcon_w is defined more than once Info: Symbol __moddi3 is defined more than once Info: Symbol __syslinux_adv_ptr is defined more than once Info: Symbol __negdi2 is defined more than once Info: Symbol __umoddi3 is defined more than once Info: Symbol __lshrdi3 is defined more than once Info: Symbol __dtors_end is defined more than once Info: Symbol __dtors_start is defined more than once Info: Symbol dev_null_r is defined more than once Info: Symbol __ashldi3 is defined more than once Info: Symbol __udivdi3 is defined more than once Info: Symbol __syslin...
2014 Jun 10
0
How to use --once? Does it work?
...tdcon_w is defined more than once > > Info: Symbol __moddi3 is defined more than once > > Info: Symbol __syslinux_adv_ptr is defined more than once > > Info: Symbol __negdi2 is defined more than once > > Info: Symbol __umoddi3 is defined more than once > > Info: Symbol __lshrdi3 is defined more than once > > Info: Symbol __dtors_end is defined more than once > > Info: Symbol __dtors_start is defined more than once > > Info: Symbol dev_null_r is defined more than once > > Info: Symbol __ashldi3 is defined more than once > > Info: Symbol __udivd...
2008 Aug 16
1
Minimal COM32 Root Module
...able size for the root module, those objects, of course, don't need to be removed. LIBENTRY_OBJS = \ sys/farcall.o sys/cfarcall.o sys/zeroregs.o \ sys/argv.o \ sys/ftell.o \ sys/isatty.o sys/fstat.o LIBGCC_OBJS = \ libgcc/__ashldi3.o \ libgcc/__negdi2.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o \ libgcc/__muldi3.o \ libgcc/__divdi3.o libgcc/__moddi3.o LIBCONSOLE_OBJS = \ sys/colortable.o sys/screensize.o \ \ sys/rawcon_write.o \ sys/null_read.o sys/null_write.o sys/serial_write.o \ \ sys/xserial_write.o \ \ sys/ansi.o \ \ sys/ansicon_write.o sys/ansise...
2012 Sep 04
0
[PATCH] console: Close stdin, stdout, stderr on ldlinux.c32 unload
...write.o fgetc.o fclose.o errno.o lmalloc.o \ sys/err_read.o sys/err_write.o sys/null_read.o \ - sys/stdcon_write.o sys/openconsole.o \ + sys/stdcon_write.o \ syslinux/memscan.o strrchr.o \ libgcc/__ashldi3.o libgcc/__udivdi3.o \ libgcc/__negdi2.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o \ diff --git a/core/extern.inc b/core/extern.inc index 3cde286..953be42 100644 --- a/core/extern.inc +++ b/core/extern.inc @@ -27,8 +27,6 @@ extern hexdump, mydump - extern printf_init - extern mem_init ; fs.c diff --git a/core/hello.c b/core/hello.c index d30fc3b..bed7cb5 100644 ---...
2015 Nov 05
0
[klibc:master] Inline __arch_libcinit()
...uild +++ b/usr/klibc/arch/i386/Kbuild @@ -2,7 +2,7 @@ # klibc .o files for i386 # -klib-y := archinit.o socketcall.o setjmp.o syscall.o varsyscall.o +klib-y := socketcall.o setjmp.o syscall.o varsyscall.o klib-y += open.o openat.o vfork.o klib-y += libgcc/__ashldi3.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o klib-y += libgcc/__muldi3.o libgcc/__negdi2.o diff --git a/usr/klibc/libc_init.c b/usr/klibc/libc_init.c index c54d022..c5b9bab 100644 --- a/usr/klibc/libc_init.c +++ b/usr/klibc/libc_init.c @@ -28,6 +28,12 @@ #include <klibc/sysconfig.h> #include "atexit.h" +#if _KLIBC_HAS_...
2014 Apr 09
0
[klibc:master] Move architecture-specific initialization to arch/
...uild +++ b/usr/klibc/arch/i386/Kbuild @@ -2,7 +2,7 @@ # klibc .o files for i386 # -klib-y := socketcall.o setjmp.o syscall.o varsyscall.o +klib-y := archinit.o socketcall.o setjmp.o syscall.o varsyscall.o klib-y += open.o openat.o vfork.o klib-y += libgcc/__ashldi3.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o klib-y += libgcc/__muldi3.o libgcc/__negdi2.o diff --git a/usr/klibc/arch/i386/archinit.c b/usr/klibc/arch/i386/archinit.c new file mode 100644 index 0000000..111d130 --- /dev/null +++ b/usr/klibc/arch/i386/archinit.c @@ -0,0 +1,18 @@ +/* + * arch/i386/archinit.c + * + * Architecture-specific l...
2016 Jan 06
0
[klibc:master] i386: remove special handling of socketcall
...a/usr/klibc/arch/i386/Kbuild +++ b/usr/klibc/arch/i386/Kbuild @@ -2,7 +2,7 @@ # klibc .o files for i386 # -klib-y := socketcall.o setjmp.o syscall.o varsyscall.o +klib-y := setjmp.o syscall.o varsyscall.o klib-y += open.o openat.o vfork.o klib-y += libgcc/__ashldi3.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o klib-y += libgcc/__muldi3.o libgcc/__negdi2.o diff --git a/usr/klibc/arch/i386/socketcall.S b/usr/klibc/arch/i386/socketcall.S deleted file mode 100644 index 44e2004..0000000 --- a/usr/klibc/arch/i386/socketcall.S +++ /dev/null @@ -1,55 +0,0 @@ -# -# socketcall.S -# -# Socketcalls use the follo...
2017 Mar 05
3
Error in Windows build from release_40 branch
Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54>
2009 Feb 11
1
[PATCH 1/1] COM32 API: Add functions for directory use
...efile +++ b/com32/lib/Makefile @@ -21,6 +21,8 @@ LIBOBJS = \ asprintf.o vasprintf.o strlcpy.o strlcat.o \ vsscanf.o zalloc.o \ \ + opendir.o readdir.o closedir.o getcwd.o chdir.o fdopendir.o \ + \ libgcc/__ashldi3.o libgcc/__udivdi3.o \ libgcc/__negdi2.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o \ libgcc/__muldi3.o libgcc/__udivmoddi4.o libgcc/__umoddi3.o \ diff --git a/com32/lib/chdir.c b/com32/lib/chdir.c new file mode 100644 index 0000000..88dceec --- /dev/null +++ b/com32/lib/chdir.c @@ -0,0 +1,13 @@ +/* + * chdir.c + */ + +#include <dirent.h> +#include <stdio.h> +#inc...