search for: eleviant

...6_64-linux/builds/18677 Is there a hole in our testing? Anyone else seeing this failure? Any idea of the cause? "hwasan_memset" doesn't appear anywhere in compiler-rt's history, but it shows up in LLVM: commit 631b5bc6125d979804e3e563935a93e2577e617c Author: Eugene Leviant <eleviant at accesssoftek.com> Date: Thu Dec 20 09:04:33 2018 +0000 [HWASAN] Add support for memory intrinsics Differential revision: https://reviews.llvm.org/D55117 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 349728 91177308-0d34-0410-b5e6-96231b3b80d8 This...

This commit has added __hwasan_memset to compiler-rt: commit 749bd83b08b7239f5d18c4e3095183919c68eb30 Author: Eugene Leviant <eleviant at accesssoftek.com> Date: Thu Dec 20 09:10:03 2018 +0000 [HWASAN] Add support for memory intrinsics This is patch complements D55117 implementing __hwasan_mem* functions in runtime Differential revision: https://reviews.llvm.org/D55554 Notes: git-svn-rev: 349730 We ru...

...et of load instructions can be forwarded from the beginning of the wr pipeline stage to either the load or store AGU base operand” However nothing is said about pre/post indexed forms. From: Andrew Trick<mailto:atrick at apple.com> Sent: 15 сентября 2020 г. 7:04 To: Evgeny Leviant<mailto:eleviant at accesssoftek.com> Cc: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> Subject: [EXTERNAL] Re: [llvm-dev] Simulation of load-store forwarding with MI scheduler on AArch64 CAUTION: This email originated from outside of the organization. Do not click links or open attachment...

I was asked this question today and frankly, I didn't know the answer. So I thought I'd post it here.... If you don't need to access greater than 4GB RAM, is there any benefit to running the 64-bit version of CentOS vs the 32-bit one? That's assuming, of course, that the target machine utilizes a 64-bit capable processor. I hadn't seen any noticeable difference, but I

I have a billing database that runs on a Faircom engine. I had set things up initially with users accessing files in this directory with their user accounts. However, only one person could enter data at a time. I then created a seperate share for this directory and did a force user= on it. I had thought that this worked, but of course users never bothered to tell me that after a short

Hi list, Is it possible to simulate load to store forwarding on aarch64 with MI scheduling model on AArch64? For instance $x0 data latency in the example below should be 1 cycle ldr $x0, [$x1] str $x0, [$x2] But it should be 4 cycles if we have another instruction: ldr $x0, [$x1] add $x0, $x0, 4 For ALU instructions it’s possible to use either ReadAdvance or SchedReadAdvance, but I don’t see

Yep, it's once again variable and it's type using different scopes. Is there any strong reason why you set scope for global DIDerivedType? ________________________________________ От: Carlo Kok <ck at remobjects.com> Отправлено: 21 марта 2018 г. 18:22 Кому: Evgeny Leviant; llvm-dev at lists.llvm.org Тема: Re: [llvm-dev] lld/lto/win32 crash on DIE code Thanks! Unfortunately this

Hello Carlo, I tried your reproducer and faced different problem from one you described (I'm using MacOS Sierra and lld built from trunk on Mar, 15). The crash happens when SelectionDAGBuilder::lowerInvokable tries to access EH info of this function: ms_t26_RemObjects_d_Elements_d_EUnit_d_Runnerb_RunChildrennt2a_RemObjects_d_Elements_d_EUnit_d_RunContext This happens because LLVM

I have a fairly recent LLD/LTO llvm crashing on DIE *ContextDIE = getOrCreateContextDIE(Context) being null for a (local) variable. (Context is a DICompileUnit in this case, but it's not present in MDNodeToDieMap so it returns null. callstack is: llc.exe!llvm::DwarfUnit::getOrCreateTypeDIE(const llvm::MDNode * TyNode) Line 718 C++ llvm::DwarfUnit::addType(llvm::DIE & Entity, const

Thanks! Unfortunately this doesn't seem to cause it, because when I fix it to match the other files (and pretty much how clang emits it:) !0 = !DIGlobalVariableExpression(var: !1, expr: !DIExpression()) !1 = !DIGlobalVariable(name: "IDispatch_UID", linkageName: "f_t2b_RemObjects_d_Elements_d_System_d_____Global.IDispatchUID", scope: !2, file: !3, type: !622, isLocal:

I`m folowing the steps on the unofficial Samba how to. I already join my WinXP box to the domain but I can`t login from my WinXP box after restart. There is an error message that sais: Windows can`t connect to the domain because the domain controller is unable or I`m using Samba-2.2.7a on red hat 9.0 with kernel 2.4.20-18.9 this is my smb.conf [global] domain logons = yes

Please send any comments. As mentioned at the end I will follow up with some patches as soon as they are cleaned up and I create some test cases. RFC: Safe Whole Program Devirtualization Enablement =================================================== High Level Summary ------------------ The goal of the changes described in this RFC is to support aggressive Whole Program Devirtualization without