search for: krylatski

There are two unexpected failures in the check-all (this check-all runs with self-build-clang): Failing Tests (2): Clang Tools :: clang-tidy/clang-tidy-diff.cpp Clang Tools :: clang-tidy/file-filter.cpp Last log: http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/builds/340/steps/ninja%20check%202/logs/stdio From: Yaron Keren [mailto:yaron.keren at gmail.com] Sent: Thursday, April

I agree, it is great. I have some regression tests (check-all) failures on Windows locally. Does the buildbot show the same? On Thu, Apr 23, 2015 at 11:16 AM Yaron Keren <yaron.keren at gmail.com> wrote: > That's great to hear! > > 2015-04-23 12:08 GMT+03:00 Fedorova, Vera <vera.fedorova at intel.com>: > >> Hi All, >> >> >> >> This is

Hi All, This is to let you know that a new buildbot for Windows native LLVM/Clang testing is established: http://lab.llvm.org:8011/builders/clang-x64-ninja-win7 . Hardware + OS configuration is: Haswell desktop with Windows 7 + Visual Studio 2013 Update 4. It is hosted by Intel and hopefully will contribute to improve quality of the LLVM/Clang on Windows being developed in the LLVM community.

+llvm-dev From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of Bader, Alexey via cfe-dev Sent: Thursday, May 30, 2019 7:31 PM To: clang-dev developer list <cfe-dev at lists.llvm.org> Subject: [cfe-dev] FYI: LLVM Phabricactor notifications. Importance: Low Hi, I think some of contributors to the Clang received a notifications about some commits done in the past. I wanted

Hi Alexey, Your reply has been a great help to me,your way of explain the different types of compilation is very detailed and easy to understand. Even so, I have a couple of questions. 1) What do yourefer by OpenCL RT? 2) Could you give me some examples of an open-source OpenCL implementation and update optimization pipeline? Thank you in advance. Regards El vie., 20 sept. 2019 a las 12:34,

I believe (and I believe it was James who pointed this out on IRC) that Phabricator pulls in all refs, and GitHub stores PR commits under refs/pull. On 5/30/19, 3:37 PM, "llvm-dev on behalf of Tom Stellard via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org> wrote: On 05/30/2019 10:04 AM, Sachkov, Alexey via llvm-dev wrote: >

Haven't seen any discussions here. Does that mean that everybody agree on appointing George Rokos to be the code owner for the projects/openmp/libomptarget source tree? If so, can we have kind of formal approval so that the code_owners.txt file is updated and questions on libomptarget go to the right person then. BTW, the nominee was discussed at the libomptarget developers meeting, and

Hi, Currently libomptarget has no code owner. Although it is part openmp project the expertise required for libomptarget is different from openmp. Georgios Rokos from IBM has agreed to be the owner of libomptarget source, so I would like to nominate Georgios Rokos who is a major contributor to libomptarget. Thanks Ravi -------------- next part -------------- An HTML attachment was

2015-05-03 21:02 GMT+09:00 Yaron Keren <yaron.keren at gmail.com>: > I now tried the extra tests and get the same failures: > > Clang Tools :: clang-tidy/clang-tidy-diff.cpp > Clang Tools :: clang-tidy/file-filter.cpp > > Takumi, I see you added requires:shell in r211831 and r220837. > > When using MSYS requires:shell is true but test fail, is it OK to >

Hello everyone, If I understand correctly after the Metadata/Value split the Metadata support of RAUW is limited by ValueAsMetadata and MDNodeFwdDecl (i.e. until cycled in MDNode are not resovled). And my question is. Is where any way to replace an MDNode which is referenced by other MDNodes w\o iterating over all MDNodes in LLMVContext to find and replace those references? Unfortunately I

Hi all. I'm looking for an advice on how to deal with inefficient code generation for Intel Nehalem/Westmere architecture on 64-bit platform for the attached test.cpp (LLVM IR is in test.cpp.ll). The inner loop has 11 iterations and eventually unrolled. Test.lea.s is the assembly code of the outer loop. It simply has 11 loads, 11 FP add, 11 FP mull, 1 FP store and lea+mov for index

Hi, Bill and Jakob. I don't quite understand. I am talking about CMOV_GR* instructions which are conservatively marked as clobbering EFLAGS in X86InstrCompiler.td. Doesn't that mean there cannot be any use of EFLAGS in subsequent instructions before it is defined by some other instruction? I also don't understand the remark about resetting EFLAGS. What kind of reset is meant? In case

On Jun 3, 2011, at 2:59 AM, Galanov, Sergey wrote: > Hi, Bill and Jakob. > > I don't quite understand. I am talking about CMOV_GR* instructions which are conservatively marked as clobbering EFLAGS in X86InstrCompiler.td. Doesn't that mean there cannot be any use of EFLAGS in subsequent instructions before it is defined by some other instruction? > > I also don't

On Jun 2, 2011, at 12:58 PM, Bill Wendling wrote: > On Jun 2, 2011, at 3:53 AM, Galanov, Sergey wrote: > >> Hi Bill. >> >> Thank you very much! Now I see my understanding was incorrect :) A dependence from a single physreg-defining instruction (like CMP or TEST) is allowed to be shared in several instructions unless that register is not clobbered (and this is what we

This sounds like llvm.org/pr13320. On 17 September 2013 18:20, Bader, Aleksey A <aleksey.a.bader at intel.com> wrote: > Hi all. > > > > I’m looking for an advice on how to deal with inefficient code generation > for Intel Nehalem/Westmere architecture on 64-bit platform for the attached > test.cpp (LLVM IR is in test.cpp.ll). > > The inner loop has 11 iterations

Hi Jakob, I've a problem related to the commit #155362. Consider the following snippet: void bar(float* f) { ... } void foo(float* f, int idx) { int hi = idx>>3; int lo = idx&7; bar(&f[hi*8+lo]); // hi*8 + lo == idx bar(&f[hi*10+lo]); } Before 155362 revision InstCombine was able to optimize hi*8+lo to idx by applying following patterns: 1. hi*8 -> hi << 3

On Fri, May 31, 2019, 10:02 AM Roman Lebedev via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Fri, May 31, 2019 at 10:55 AM Manuel Klimek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > We should be able to control the noise of these > > >, but I also wonder whether we can switch to github reviews as part of > the git move :) >

Hi, I'm trying to get AA results for two pointers, but it seems that AA cannot look though a memcpy. For example: define dso_local spir_func void @fun() { entry: ; Store an address of `var' %var = alloca i32, align 4 store i32 42, i32* %var, align 4 %var.addr = alloca i32*, align 8 store i32* %var, i32** %var.addr, align 8 ; Memcpy

Hi Alexey, Thank you very much for your detailed reply, will look into the resources indicated. I'd like to avoid C++ if possible, let me see how it goes. Regards, Rajesh Jayaprakash On Tue 12 Mar, 2019, 6:35 PM Sachkov, Alexey, <alexey.sachkov at intel.com> wrote: > Hi Rajesh, > > If I understand correctly, libclang is a C interface to Clang features, > not LLVM. That

Hello. I am not sure this is the right place to ask but here is my question. About a year ago there was a fix of some obscure bug (rdar://problem/8030636 which is located on the internal Apple bugtracker I believe and so not available to the general public :)) Some discussion can be found here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100531/102160.html. Unfortunately, no