search for: leviant

...: true) It still crashes. Same callstack. Note that all these .o files individually compile file, it's only when I let the linker lto-merge them things go wrong for me. (updated https://www.dropbox.com/s/n3e2eystps9qvwx/repro.tar?dl=0 to reflect above) Op 21-3-2018 om 11:58 schreef Evgeny Leviant: > Ok, I've done a bit more investigation. I found the module which declares broken DIE > (e54b3dc8c0536e29a65f8548b5ae7958-Global.o) and here is what I found there: > > !2 = !DIFile(filename: "island.windows.elements", ... > ... > !4 = distinct !DICompileUnit(langu...

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 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 = !DI...

Op 21-3-2018 om 10:28 schreef Evgeny Leviant: > It looks the problem lies in how your compiler generates debug info. LLVM doesn't > expect DIDerivedType scope to be an instance of DICompileUnit. Here is a quick fix: > > DIE *DwarfUnit::getOrCreateContextDIE(const DIScope *Context) { > - if (!Context || isa<DIFile>...

...bsequent DIEs reference file !2, except DICompileUnit (!4) which references file !5. This seems a bit strange for me. Can't this be a root cause of your problems? ________________________________________ От: Carlo Kok <ck at remobjects.com> Отправлено: 21 марта 2018 г. 12:31 Кому: Evgeny Leviant; llvm-dev at lists.llvm.org Тема: Re: [llvm-dev] lld/lto/win32 crash on DIE code Op 21-3-2018 om 10:28 schreef Evgeny Leviant: > It looks the problem lies in how your compiler generates debug info. LLVM doesn't > expect DIDerivedType scope to be an instance of DICompileUnit. Here is a qu...

...a from a limited set 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...

...sanitizer-x86_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-96231b...

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:...

Op 16-3-2018 om 20:16 schreef Evgeny Leviant: > 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...

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

...e expects either pointer to a filter function or null in first operand, while you're passing pointer to structure: catchpad within %80 [{i8*, i8*}* anon..., ...] ________________________________________ От: Carlo Kok <ck at remobjects.com> Отправлено: 20 марта 2018 г. 11:04 Кому: Evgeny Leviant; llvm-dev at lists.llvm.org Тема: Re: [llvm-dev] lld/lto/win32 crash on DIE code Op 16-3-2018 om 20:16 schreef Evgeny Leviant: > 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...

...|| isa<DICompileUnit>(Context)) However, I suggest talking to someone with in-depth debug info experience, as the problem itself seems to be not related to LTO. ________________________________________ От: Carlo Kok <ck at remobjects.com> Отправлено: 20 марта 2018 г. 17:50 Кому: Evgeny Leviant; llvm-dev at lists.llvm.org Тема: Re: [llvm-dev] lld/lto/win32 crash on DIE code Op 20-3-2018 om 12:40 schreef Evgeny Leviant: > This one triggers an assertion in calculateSEHStateNumbers due to weird catchpad instruction > in @_island_debug_invoke and many other functions. The code expects...

I'm using Speex in Windows VoIP application and trying to implement echo cancellationI'm using waveInXXXX and waveOutXXXX API. I'm doing quite simple thing: After buffer is played (I get MM_WOM_DONE message) I'm just copying it's content to temporary playback buffer After buffer is recorded (I get MM_WIM_DONE message) I call speex_echo_cancellation(state, recorded_buf,

Op 20-3-2018 om 12:40 schreef Evgeny Leviant: > This one triggers an assertion in calculateSEHStateNumbers due to weird catchpad instruction > in @_island_debug_invoke and many other functions. The code expects either pointer to a filter > function or null in first operand, while you're passing pointer to structure: > > ca...

...I think the additional flexibility is worth it. > > [*] Mapping symbols identify ranges of ARM code ($a), Thumb code ($t) > and literal data ($d). It would be great to add these to Thunks and > PLT entries as this would improve disassembly. > > On 19 October 2016 at 10:37, Eugene Leviant via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > I would suggest converting only part of linker generated sections to > > input sections to reduce amount of code changes. > > For example it's unlikely that SymbolTableSection or > > StringTableSection would...

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

I would suggest converting only part of linker generated sections to input sections to reduce amount of code changes. For example it's unlikely that SymbolTableSection or StringTableSection would ever require such treatment, so why converting them to input sections? 2016-10-19 11:03 GMT+03:00 George Rimar <grimar at accesssoftek.com>: >>This idea popped up in the review thread

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

Hi, Everyone! I'm developing VoIP application using Speex, have some questions: 1) When ultra-wideband mode should I use 32000 Hz sampling rate only? If I use 44100 Hz the voice quality seems to be better comparing to 32 KHz. 2) When I use wideband mode with 16 KHz sampling rate bandwidth usage is greater comparing to 32 KHz, ultra-wideband. Why? Voice quality is worse when using 16KHz