search for: malyutin

...it was straightforward) and applied it in my fork. It seems to have solved one of the problems I was having. Would LLVM be interested if I submit the updated version for the review? -- Danila From: Philip Reames [mailto:listmail at philipreames.com] Sent: Tuesday, August 13, 2019 19:01 To: Danila Malyutin <Danila.Malyutin at synopsys.com>; Finkel, Hal J. <hfinkel at anl.gov> Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] How to best deal with undesirable Induction Variable Simplification? Wasn't aware of this patch. No, I don't see an obvious reason why it wasn't f...

I've noticed that there was an attempt to mitigate ExitValues problem in https://reviews.llvm.org/D12494 that went nowhere. Were there particular issues with that approach? -- Danila From: Philip Reames [mailto:listmail at philipreames.com] Sent: Saturday, August 10, 2019 02:05 To: Danila Malyutin <Danila.Malyutin at synopsys.com>; Finkel, Hal J. <hfinkel at anl.gov> Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] How to best deal with undesirable Induction Variable Simplification? On 8/9/19 8:27 AM, Danila Malyutin via llvm-dev wrote: Hi Hal, I see. So LSR could theor...

...;offset", which leads to the extra spills since they all live across big loop body. When exit values are not rewritten 'a' stays in it's `r15d` register with no extra costs. -- Danila From: Finkel, Hal J. [mailto:hfinkel at anl.gov] Sent: Thursday, August 8, 2019 21:24 To: Danila Malyutin <Danila.Malyutin at synopsys.com> Subject: Re: [llvm-dev] How to best deal with undesirable Induction Variable Simplification? Hi, Danila, Regarding the first case, this is certainly a problem that has come up before. As I recall, and I believe this is still true, LoopStrengthReduce, whe...

Hello, Recently I've come across two instances where Induction Variable Simplification lead to noticable performance regressions. In one case, the removal of extra IV lead to the inability to reschedule instructions in a tight loop to reduce stalls. In that case, there were enough registers to spare, so using extra register for extra induction variable was preferable since it reduced

...ee some additional test coverage there[1]. > > - Matthias > > > [1] I personally am a compiler developer with little experience in web development. I don't know what strategies exist to test javascript embedded in a webpage... > >> On Jun 28, 2018, at 9:48 AM, Danila Malyutin via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> Hello. >> We’ve started using LNT and found it very handy. However, we found that LNT web UI is missing some features to help our use-cases. >> We’d like to add them (and...

Hi, we at Arm have noticed that assembly can differ when compiling for AArch64 depending on whether debug information is generated or not. The issue is reproducible for the following small example compiled with `-O1` for `aarch64-arm-linux-gnu`: a() { b(a); for (;;) c("", b); } The reason for the difference is that AArch64 frame lowering emits CFI

Hello. We've started using LNT and found it very handy. However, we found that LNT web UI is missing some features to help our use-cases. We'd like to add them (and already started doing so) but it's hard to add them without breaking existing features/workflows because while LNT has some python CLI test coverage the dynamic Web part (mainly JS UI) is not really tested. So our question

On Thu, Jun 25, 2020 at 11:43 AM Nikita Popov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Thu, Jun 25, 2020 at 11:22 AM Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> What this means for LLVM is that everyone will have to completely stop using history rewriting operations. No more rebase, squash, amend, etc. > > This is also incorrect. Most