similar to: [LLVMdev] possible miscompilation of openssl on x86-64

Hello, I have tried to compile openssh-3.1p1 and then two later snapshots. It seems that I can not have support for KTH-Krb4, according to this errorlist from make: gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -R/usr/local/ssl/lib -L/usr/local/ssl/lib -L/usr/local/lib -R/usr/local/lib -L/usr/athena/lib -R/usr/athena/lib -lssh

Jan, maybe I should check the /afs information that you pointed me at in a subsequent email first, but I wanted to update you on what happened following this path: I did get some mileage out of both of your suggestions below, but still did not make it through (now working with openssh-2.9p2): gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L.

Hello All, During the make of openssh-2.9 on solaris 5.8 make failed with the following error: ld: fatal: symbol `des_check_key' is multiply-defined: (file /xxx/xxx/solaris/admin/sys/krb4/lib/libdes.a(set_key.o) and file / xxx/xxx/solaris/openssl/lib/libcrypto.a(set_key.o)); ld: fatal: symbol `des_set_odd_parity' is multiply-defined: (file

Hi , I shared linux directory which is mounted using ecryptfs to a windows 10 client using samba share . When i do a robocopy of file greater than size of 7GB the samba throws an error NT Status: STATUS_OBJECT_NAME_NOT_FOUND which can be observed in wire shark  . Setup : ---------- Host with ubuntu 16.01  -------------------> windows 10 client (Samba

I shared raid 5 array which is mounted using ecryptfs to a windows 10 client using samba share . When i do a robocopy of file greater than size of 7GB the samba throws an error NT Status: STATUS_OBJECT_NAME_NOT_FOUND which can be observed in wire shark . Setup : ---------- Host with ubuntu 16.01 -------------------> windows 10 client (Samba server,

I've got a problem that I'm hoping the list can help with, otherwise ... Heres the problem, I've got OpenSSH 1.2.2p1 running on my Intel Linux box as the secure server. I can connect from another Intel Linux box using scp and it all seems to work fine. Another box tries to connect and it gets a warning about the host keysize not matching. I'm thinking this could be some byte

Hi List ;) im currently playing around with the newest tinc1.1pre7 sources... After some tests which were all successful so far, id like to know if its possible to change the default RSA KeySize from 2048 to 4096 (or what ever). For example: its not possible to change the key size when im executing tinc -n NETNAME init NAME Ok, i know that i can pass the key length as parameter when i call

Scenario: Use the ssh-keygen utility in openssh-1.2pre17 to generate a host key Kill and restart sshd Remove the old host key from ~/.ssh/known_hosts Connect to the host using ssh. I get this: homer.ka9q.ampr.org$ ssh 199.106.106.3 who The authenticity of host '199.106.106.3' can't be established. Key fingerprint is 1024 a0:8d:17:f0:fa:a9:9f:6f:b5:d0:1c:d6:02:92:bd:5e. Are you sure

Hi Tim, The verbose mode is a good idea, thank you. I've gathered all compilation commands with -v flag for clang-4 and clang-5 and they are identical (excerpt of compiler version). I will try to find what has changed in clang/llvm between the versions. If there are any other hints: send them my way :) > On 31. May 2018, at 09:54, Tim Northover <t.p.northover at gmail.com> wrote:

http://llvm.org/bugs/show_bug.cgi?id=1837 I reduced the above case to this: ; test.ll define i8* @test() { %x1 = malloc i8, i32 16 %x2 = bitcast i8* %x1 to i8** store i8* %x1, i8** %x2 ret i8* %x1 } $ llvm-as test.ll $ opt -instcombine test.bc -o testopt.bc $ llc test.bc $ llc testopt.bc $ diff -u test.s testopt.s -movl $16, (%esp) +movl $8, (%esp) call malloc I'm afraid that I'm not

I don't think C has a way to express 32b x 32b -> 64b multiply, even though there is (on x86 anyway) a hardware instruction that does it. The type of your expression (x * y) is still uint32_t. The implicit type coercion up to uint64_t as part of the return statement doesn't change this. On Jan 13, 2008, at 10:29 PM, Zhou Sheng wrote: > Hi, > > Here is C function: >

Can you please attach IR which can be compiled to an executable (and shows the problem). Thanks! Duncan.

Hello, I have this simple IR: ------------------------------------------------------------------------ define internal i32 @tmp(i32 %x) { entry: br label %entry2 entry2: %x1 = alloca i32 %x2 = alloca i32 %retval = alloca i32 %dummy = alloca i32 store i32 %x, i32* %x1 store i32 %x, i32* %x2 %tmp1 = load i32* %x1 %tmp2 = add i32 %tmp1, %tmp1

Hello, Julien > I have this simple IR: That's probably my bug somewhere :) I'm also seeing the difference. Will try to investigate. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Julien > Any idea why this is happening ? I think I fixed this. Please verify. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

What target are you compiling for? Ciao, Duncan.

Sorry to ask about a documented use of bugpoint, but I am having trouble understanding what to do. I would like to be able to use bugpoint to simplify test cases, when the symptom is a run time difference in the testprogram behavior. That looks like what is described in the documentation as "miscompilation or perhaps code generation problems". There are examples in the LLVM doc showing

Hi David, > It then iterates until a simplified test case is created whose output is > still different from that of the native code. isn't that exactly what you want: a small test-case that shows the problem? Ciao, Duncan.

Yes, its what I want, but I can't figure out how to get bugpoint to accomplish this. -David ________________________________ From: Duncan Sands [mailto:baldrick at free.fr] Sent: Thu 2/18/2010 6:06 AM To: David Dunkle Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] using bugpoint to find miscompilation/code generation problems? Hi David, > It then iterates until a simplified test

Using clang r107598 at -O1 to create reportable SPECINT 2006 results, I'm getting the output below, which is almost certainly due to a miscompilation. Known problem? Thanks, John Running (#3) 403.gcc ref base i386-m32-gcc42-nn default /home/regehr/z/specCPU2006/bin/specinvoke -d /home/regehr/z/specCPU2006/benchspec/CPU2006/403.gcc/run/run_base_ref_i386-m32-gcc42-nn.0000 -e