search for: kanthak

On Tue, Dec 4, 2018 at 3:58 PM Daniel Sanders via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Dec 4, 2018, at 15:11, Stefan Kanthak <stefan.kanthak at nexgo.de> wrote: > No, I understand his intent. I just doesn't align with my intent, > including the hoops he/LLVM wants me to jump through. > > He's not saying they're your bugs, he's just saying they need > to be reported in the correct plac...

Hi there, I have seen in the file column plugin ( http://www.kanthak.net/opensource/file_column/) from Sebastian Kanthak or David''s acts_as_taggable plugin that to register my functionality I need to do something like this: ApplicationHelper.send(:include, InPlaceEditAssociations) I am wondering why not: (a) module ApplicationHelper include InPlaceEdit...

"Tim Northover" <t.p.northover at gmail.com> wrote: > Hi, > > On Sat, 1 Dec 2018 at 17:37, Stefan Kanthak via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Compile the following functions with "-O3 -target amd64" > > You've been advised before, but you really need to start reporting > these as bugs[*] if you actually care about them. These ain't my bugs,...

...tribution guidelines here : https://llvm.org/docs/Contributing.html LLVM also have code of conduct : https://llvm.org/docs/CodeOfConduct.html On Sun, 23 Aug 2020 at 23:28, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Sun, Aug 23, 2020 at 10:54 AM Stefan Kanthak <stefan.kanthak at nexgo.de> > wrote: > >> "David Blaikie" <dblaikie at gmail.com> wrote: >> >> > Context is everything. >> >> I'm willing to accept your humble apologies. >> > > Sarcasm and snark are not appreciated. Your...

"H. Peter Anvin" <hpa at zytor.com> wrote August 20, 2019 12:51 AM: > 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 cod...

...dbolt. _my_bswap: 1f70: 55 pushl %ebp 1f71: 89 e5 movl %esp, %ebp 1f73: 8b 55 08 movl 8(%ebp), %edx 1f76: 8b 45 0c movl 12(%ebp), %eax 1f79: 0f c8 bswapl %eax 1f7b: 0f ca bswapl %edx 1f7d: 5d popl %ebp 1f7e: c3 retl ~Craig On Sun, Nov 25, 2018 at 11:39 AM Stefan Kanthak <stefan.kanthak at nexgo.de> wrote: > "Craig Topper" <craig.topper at gmail.com> wrote: > > > bswapdi2 for i386 is correct > > OUCH! > > > Bits 31:0 of the source are loaded into edx. Bits 63:32 are loaded into > > eax. Those are each bswapped...

...; wrote: > bswapsi2 on the x86-64 isn't using the bswap instruction because "unsigned > long" is 64-bits on x86-64 linux. But its 32-bits on x86-64 msvc. > > Not sure about the bswapdi2 i386 case. > > > ~Craig > > > On Sun, Nov 25, 2018 at 8:03 AM Stefan Kanthak via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi @ll, >> >> targetting i386, LLVM/clang generates wrong code for the following >> functions: >> >> unsigned long __bswapsi2 (unsigned long ul) >> { >> return (((ul) & 0xff0...

...put INVERSE text, which would be even more outstanding and easier to spot. Also: starred **** borders are not as outstanding as hashed #### or slashed //// borders! Now go and fix the bug resulting in the crash I demonstrated below! Stefan > On Sun, Aug 23, 2020 at 5:21 AM Stefan Kanthak via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Who's "shouting" here? Even in complete lines, 9 consecutive words! >> >> >> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: >> Preprocessed source(s) and associated run script(s) a...

...rax, rcx mov rcx, rdi shl rcx, 8 and ecx, 16711680 or rax, rcx and rdi, 255 shl rdi, 24 or rax, rdi ret __bswapdi2: # @__bswapdi2 bswap rdi mov rax, rdi ret Both are correct, but __bswapsi2() should of course use BSWAP too! Stefan Kanthak PS: for comparision with another compiler, take a look at <https://skanthak.homepage.t-online.de/msvc.html#example5>

...n and should be avoided. Use the following better code sequences instead: 1: 1: shll %cl,%eax shrl %cl,%edx movl %eax,%edx movl %edx,%eax xorl %eax,%eax xorl %edx,%edx ret ret regards Stefan Kanthak PS: I doubt that a current GCC emits calls of the routines in the /usr/klibc/arch/i386 subdirectory any more.

...erver"). This works well here since more than 10 years now. Recently I created a subdirectory "syslinux" in my "tftpboot" ... and PXELINUX failed with the message "unable to locate configuration file". Renaming that directory works around the bug. regards Stefan Kanthak

...rce tree without clobbering existing files. The same holds for __alldiv, __alldvrm, __allrem, __aulldiv, __aulldvrm and __aullrem, plus __allmul, __allshl, _allshr and __aullshr. If you name a reviewer I'll send them to llvm-commits! regards Stefan > On Mon, Dec 3, 2018 at 5:51 AM Stefan Kanthak via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi @ll, >> >> LLVM-7.0.0-win32.exe contains and installs >> lib\clang\7.0.0\lib\windows\clang_rt.builtins-i386.lib >> >> The implementation of (at least) the multiplication and division >&gt...

...neg eax | shr edi | shr edi | sbb eax, eax and eax, esi | and eax, esi xor eax, edi | xor eax, edi ret | ret See <https://godbolt.org/z/aPKweG> regards Stefan Kanthak > Which is this in LLVM IR: > define i32 @foo(i32 %x) { > %t2 = icmp slt i32 %x, 0 > %t3 = shl i32 %x, 1 > %t4 = xor i32 %t3, -306674912 > %t5 = select i1 %t2, i32 %t4, i32 %t3 > ret i32 %t5 > } > > Please a file a bug report for the x86 backend (including perfo...

...a step back, walk away from a couple of days, and if you > want to reengage with a calmer perspective at that time, then do so. Take a step back and change your point of view until you get the right perspective, then fix the couple of bugs I presented! Stefan > On 8/21/20 10:41 AM, Stefan Kanthak via llvm-dev wrote: >> "David Greene" <dag at hpe.com> wrote: >> >>> Stefan Kanthak via llvm-dev <llvm-dev at lists.llvm.org> writes: >>> >>>> "Michael Kruse" <llvmdev at meinersbur.de> wrote: >>>> >>&...

Objects compiled for the MS-ABI don't conform to it! Data types beyond 64 bit MUST BE returned by the callee via the hidden first argument allocated by the caller, NOT in XMM0! Demo/proof: from this source --- llvm-bug.c --- #ifndef __clang__ typedef struct { unsigned __int64 low; unsigned __int64 high; } __uint128_t; #else __attribute__((ms_abi)) #endif __uint128_t

...) are located at: clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.c clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.sh clang: note: diagnostic msg: ******************** --- crash-74a40f.c --- # 1 "<built-in>" # 1 "crash.c" // Copyright (C) 2020 Stefan Kanthak <stefan.kanthak at nexgo.de> long dummy; __attribute__((naked)) long function(void) { __asm__(".data\n" "dummy:\n" ".quad\t0\n" ".text\n" ".intel_syntax noprefix\n" "\tmov\trax,...

...y/ff770578.aspx>, <https://msdn.microsoft.com/en-us/library/ff770583.aspx>, <https://msdn.microsoft.com/en-us/library/ff770597.aspx>, <https://msdn.microsoft.com/en-us/library/ff770588.aspx>, <https://msdn.microsoft.com/en-us/library/ff770595.aspx> regards Stefan Kanthak PS: Howard Hinnant, (one of) the original author of the builtins library, is still listed in compiler-rt/CODE_OWNERS.TXT, despite having left this project about TEN years ago! To quote himself: | I haven't worked on compiler_rt in any way for at least a decade. | Sorry for your poo...

...not accept email, basically - I'm one of the moderators there & any email sent there that doesn't come from the bug database will get automatically or manually rejected with the suggestion/request that the bug database is used instead. > > On Tue, Nov 27, 2018 at 4:37 PM Stefan Kanthak <stefan.kanthak at nexgo.de> > wrote: > >> "Sanjay Patel" <spatel at rotateright.com> wrote: >> >> > IIUC, you want to use x86-specific bit-hacks (sbb masking) in cases like >> > this: >> > unsigned int foo(unsigned int crc) { >&...

...| ret sar edx, 31 ret NOTE: not just here this sequence SHOULD be replaced with mov edx, eax | cdq sar edx, 31 Although CDQ is the proper instruction for sign extension, LLVM/clang doesn't seem to like it. stay tuned Stefan Kanthak

.../builtins/i386/ contains FAR better (although suboptimal) __divdi3, __moddi3, __udivdi3 and __umoddi3 routines written in assembler, which SHOULD be shipped with clang_rt.builtins-i386.lib instead of the above listed POOR and NOT optimised implementations! NOT AMUSED Stefan Kanthak PS: <https://lists.llvm.org/pipermail/llvm-dev/2018-November/128094.html> has patches for the assembler routines! PPS: please remove the blatant lie | The builtins library provides optimized implementations of | this and other low-level routines, either in target-independent...