[clang] [llvm] [AMDGPU][WIP] Extend readlane, writelane and readfirstlane intrinsic lowering for generic types (PR #89217)

@@ -342,6 +342,22 @@ def AMDGPUfdot2_impl : SDNode<"AMDGPUISD::FDOT2", def AMDGPUperm_impl : SDNode<"AMDGPUISD::PERM", AMDGPUDTIntTernaryOp, []>; +def AMDGPUReadfirstlaneOp : SDTypeProfile<1, 1, [ + SDTCisSameAs<0, 1> +]>; + +def AMDGPUReadlaneOp : SDTypeProfile<1, 2, [ +

[clang] 26041e1 - Update link job for flang on windows

Author: Diana Picus Date: 2022-06-20T07:25:10Z New Revision: 26041e17006cf30e9c2d06706fe6bd3fa818e356 URL: https://github.com/llvm/llvm-project/commit/26041e17006cf30e9c2d06706fe6bd3fa818e356 DIFF: https://github.com/llvm/llvm-project/commit/26041e17006cf30e9c2d06706fe6bd3fa818e356.diff LOG:

Re: [llvm-dev] Zorg migration to GitHub/monorepo

Hi Galina, On Tue, 29 Oct 2019 at 04:42, Galina Kistanova wrote: > > Hello Nemanja, > > > a commit to a project that shouldn't trigger builds on a libcxx bot (i.e. > > the change was in llvm). > > With all due respect, this does not sound right. > I'm not sure how changes in a code a particular

Re: Zorg migration to GitHub/monorepo

Hi Galina, It seems that our libcxx bots are now triggering builds for any changes to llvm: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux/builds/2434 Should I file a bug report for this? Thanks, Diana On Sat, 19 Oct 2019 at 11:36, Galina Kistanova via cfe-commits

Re: [PATCH] D53137: Scalable vector core instruction support + size queries

Hi Graham, It seems you forgot to push the last round of fixes. Just saying :) Cheers, Diana On Tue, 8 Oct 2019 at 16:01, Graham Hunter via Phabricator wrote: > > huntergr added a comment. > > Hmm, forgot to add the last round of minor fixes before committing. Sorry > about that, will push

Re: [llvm-dev] Attention bot owners

Hi Galina, Thanks for the heads up. On Fri, 11 Oct 2019 at 21:09, Galina Kistanova via llvm-dev wrote: > > Hello all bots owners, > > As all of you know we move to github monorepo very soon now. > We are actively working on the buildbot to prepare a solution to switch from > SVN to github when

Re: r369591 - [LifetimeAnalysis] Support more STL idioms (template forward declaration and DependentNameType)

Hi Matthias, It seems this is breaking some of our AArch64 bots: http://lab.llvm.org:8011/builders/clang-cmake-aarch64-quick/builds/19691 http://lab.llvm.org:8011/builders/clang-cmake-aarch64-global-isel/builds/12022 You probably didn't notice it because something else also failed in that build

Re: [clang-tools-extra] r349496 - [clangd] BackgroundIndex rebuilds symbol index periodically.

Thanks, Ilya! On Mon, 7 Jan 2019 at 12:22, Ilya Biryukov wrote: > > Temporarily disabled the test in r350512. > > On Mon, Jan 7, 2019 at 10:54 AM Diana Picus wrote: >> >> Hi Eric, >> >> This is still failing intermittently on AArch64 in spite of your and >> Ilya's timeout increases. Could you

Re: [clang-tools-extra] r349496 - [clangd] BackgroundIndex rebuilds symbol index periodically.

Hi Eric, This is still failing intermittently on AArch64 in spite of your and Ilya's timeout increases. Could you please revert and rework this test? Thanks, Diana http://lab.llvm.org:8011/builders/clang-cmake-aarch64-lld/builds/5872

Re: [clang-tools-extra] r312134 - [clang-tidy] Improve hicpp-exception-baseclass to handle generic code better

On 30 August 2017 at 18:29, Jonas Toth wrote: > Hi Diana, > > i will investigate this issue. Can i see from somewhere, what email my > buildbot uses? I actually don't know if you can check anywhere, but in principle it should be the same address that the commit email came

Re: [clang-tools-extra] r312134 - [clang-tidy] Improve hicpp-exception-baseclass to handle generic code better

Hi Jonas, Usually the buildbots send emails when you're in the commit range. I'm surprised that you haven't received anything. Are you sure you don't have some mail filters that are catching them and sending them somewhere unexpected? In any case, you can see a live-but-slow buildbot status

Re: [clang-tools-extra] r312134 - [clang-tidy] Improve hicpp-exception-baseclass to handle generic code better

Hi Jonas, I haven't seen any commit from you (*) fixing the buildbot failures caused by your previous commit (r312122). This has been keeping several bots red for quite a while: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/10590

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

roblem with va_arg handling. > > Sorry again that this is going so slowly... > > On 15 August 2017 at 16:52, Diana Picus <diana.pi...@linaro.org> wrote: >> On 15 August 2017 at 01:25, Richard Smith <rich...@metafoo.co.uk> wrote: >>> On 14 August 2017 at 03:27, Di

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

On 15 August 2017 at 01:25, Richard Smith <rich...@metafoo.co.uk> wrote: > On 14 August 2017 at 03:27, Diana Picus via cfe-commits > <cfe-commits@lists.llvm.org> wrote: >> >> Hi, >> >> Strangely enough, it turns out that if I run >> Asan-armhf-wit

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

t;>>> >>>>>>>>>> Hi again, >>>>>>>>>> >>>>>>>>>> I finally got the debug build, but unfortunately the stack traces >>>>>>>>>> that >>>>>>>>>>

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

gt;>>>>>>> the tests print look the same. My suspicion is that this is because >>>>>>>>> the addresses printed by the tests are funny (i.e. odd numbers >>>>>>>>> instead >>>>>>>>> of

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

dresses in an objdump >>>>>>>> of >>>>>>>> the executable, but I didn't have much success since most of them >>>>>>>> weren't really pointing to call instructions. >>>>>>>> >&g

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

ey pass. >>>>>> >>>>>> I'm not sure what else to try. Thoughts? >>>>>> >>>>>> Thanks, >>>>>> Diana >>>>>> >>>>>>> On 11 August 2017 at 11:14, Diana Picus <diana.pi...@

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

>>>> else to reboot it because I can't power cycle it remotely). I can >>>> assure you this is one of my top priorities, I'll get those stack >>>> traces as soon as I can. >>>> >>>> Thanks for your patience and sorry again, >>>> Dian

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

u this is one of my top priorities, I'll get those stack >>> traces as soon as I can. >>> >>> Thanks for your patience and sorry again, >>> Diana >>> >>>> On 10 August 2017 at 22:55, Richard Smith <rich...@metafoo.co.uk> wrote: >>>&

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

on this? We want this change in Clang 5, so the sooner we can >> understand and fix this regression the better... >> >> On 10 August 2017 at 01:28, Diana Picus via cfe-commits >> <cfe-commits@lists.llvm.org> wrote: >>> >>> Hi Vassil, >>>

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

tand and fix this regression the better... > > On 10 August 2017 at 01:28, Diana Picus via cfe-commits > <cfe-commits@lists.llvm.org> wrote: >> >> Hi Vassil, >> >> My build is in progress, but since it's a full build it's probably >> going to take another co

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

ana >>> >>> On 9 August 2017 at 15:02, Vassil Vassilev <v.g.vassi...@gmail.com> >>> wrote: >>>> >>>> Hi Diana, >>>> >>>>It seems the service is down. Could you send us the details of the >>>> failures

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

something fishy going on. > > Regards, > Diana > > On 9 August 2017 at 15:02, Vassil Vassilev <v.g.vassi...@gmail.com> wrote: >> Hi Diana, >> >> It seems the service is down. Could you send us the details of the >> failures (incl stack traces if any) >> >&g

Re: r310401 - PR19668, PR23034: Fix handling of move constructors and deleted copy

Hi Richard, I'm sorry but I've reverted this in r310464 because it was breaking some ASAN tests on this bot: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full/builds/9452 Please let me know if I can help debug this. Cheers, Diana On 8 August 2017 at 21:14, Richard Smith via

r310464 - Revert "PR19668, PR23034: Fix handling of move constructors and deleted copy constructors when deciding whether classes should be passed indirectly."

Author: rovka Date: Wed Aug 9 05:22:25 2017 New Revision: 310464 URL: http://llvm.org/viewvc/llvm-project?rev=310464=rev Log: Revert "PR19668, PR23034: Fix handling of move constructors and deleted copy constructors when deciding whether classes should be passed indirectly." This reverts

Re: r305239 - Revert r301742 which made ExprConstant checking apply to all full-exprs.

Hi, I reverted r305287, since the bots were red for a very long time. More bots with the same error: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full/builds/7727 http://lab.llvm.org:8011/builders/clang-x86-windows-msvc2015/builds/5503

r305287 - Revert "Revert r301742 which made ExprConstant checking apply to all full-exprs."

Author: rovka Date: Tue Jun 13 07:50:06 2017 New Revision: 305287 URL: http://llvm.org/viewvc/llvm-project?rev=305287=rev Log: Revert "Revert r301742 which made ExprConstant checking apply to all full-exprs." This reverts commit r305239 because it broke the buildbots (the diag-flags.cpp test is

r304211 - Fixup r304205 - Require PowerPC target

Author: rovka Date: Tue May 30 09:05:33 2017 New Revision: 304211 URL: http://llvm.org/viewvc/llvm-project?rev=304211=rev Log: Fixup r304205 - Require PowerPC target Modified: cfe/trunk/test/CodeGen/altivec-ct.c Modified: cfe/trunk/test/CodeGen/altivec-ct.c URL:

Re: r304201 - [ARM] Fix Neon vector type alignment to 64-bit

Hi Javed, I think this broke the bots: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/7620 Can you have a look, or revert? Thanks, Diana On 30 May 2017 at 12:12, Javed Absar via cfe-commits wrote: > Author: javed.absar > Date: Tue May 30 05:12:15

Re: r302750 - PR22877: When constructing an array via a constructor with a default argument

On 11 May 2017 at 21:14, Richard Smith wrote: > Thanks for the revert, fixed up and recommitted in r302817. > > Any idea why not a single buildbot sent me any email about this? :( (A > couple of them were red at the previous change too, but some of them were > not (eg.

Re: r302750 - PR22877: When constructing an array via a constructor with a default argument

Hexagon too: http://lab.llvm.org:8011/builders/clang-hexagon-elf/builds/7916 On 11 May 2017 at 10:27, Diana Picus wrote: > Hi Richard, > > I reverted this and its fixup in r302776 since some of the ARM bots > were still broken: >

Re: r302750 - PR22877: When constructing an array via a constructor with a default argument

Hi Richard, I reverted this and its fixup in r302776 since some of the ARM bots were still broken: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/6969 http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15/builds/6959

r302776 - Revert "PR22877: When constructing an array via a constructor with a default argument in list-initialization, run cleanups for the default argument after each iteration of the initialization

Author: rovka Date: Thu May 11 03:10:41 2017 New Revision: 302776 URL: http://llvm.org/viewvc/llvm-project?rev=302776=rev Log: Revert "PR22877: When constructing an array via a constructor with a default argument in list-initialization, run cleanups for the default argument after each iteration

Re: r294177 - [AVR] Allow specifying the CPU on the command line

Hi Dylan, I reverted this in r294180 because I think it broke some of the buildbots. See for example http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/3599 http://lab.llvm.org:8011/builders/clang-x86-windows-msvc2015/builds/2271 Sorry, Diana On 6 February 2017 at 10:07, Dylan McKay

r294180 - Revert "[AVR] Allow specifying the CPU on the command line"

Author: rovka Date: Mon Feb 6 05:35:42 2017 New Revision: 294180 URL: http://llvm.org/viewvc/llvm-project?rev=294180=rev Log: Revert "[AVR] Allow specifying the CPU on the command line" This reverts commit r294177. It seems to have broken some buildbots. Removed:

Re: [clang-tools-extra] r293217 - Implement a new clang-tidy check that suggests users replace dynamic exception specifications with noexcept exception specifications.

Hi Don, Hi Aaron, I had to revert this in r293267 because all the clang-tools-extra buildbots were still broken many hours after it was committed. See for instance http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/1039 Eugene Zelenko also had some small fixes to

[clang-tools-extra] r293267 - Revert "Implement a new clang-tidy check that suggests users replace dynamic exception specifications with noexcept exception specifications."

Author: rovka Date: Fri Jan 27 01:19:22 2017 New Revision: 293267 URL: http://llvm.org/viewvc/llvm-project?rev=293267=rev Log: Revert "Implement a new clang-tidy check that suggests users replace dynamic exception specifications with noexcept exception specifications." This reverts commit

Re: r293004 - Use filename in linemarker when compiling preprocessed source

Erm, the revert was actually r293032, sorry about the confusion. On 25 January 2017 at 09:34, Diana Picus wrote: > Hi David, > > Sorry, but I had to revert this (r283029) because it was breaking the > non-x86 buildbots (arm, powerpc, hexagon), with errors along the lines

r293032 - Revert "Use filename in linemarker when compiling preprocessed source"

Author: rovka Date: Wed Jan 25 01:27:05 2017 New Revision: 293032 URL: http://llvm.org/viewvc/llvm-project?rev=293032=rev Log: Revert "Use filename in linemarker when compiling preprocessed source" This reverts commit r293004 because it broke the buildbots with "unknown CPU" errors. I tried to

Re: r293004 - Use filename in linemarker when compiling preprocessed source

Hi David, Sorry, but I had to revert this (r283029) because it was breaking the non-x86 buildbots (arm, powerpc, hexagon), with errors along the lines of: error: unknown target CPU 'cortex-a8' Please recommit after you've fixed the issue. Thanks, Diana PS: I tried to fix it in r293024, but

r293026 - Try to fix test from r293004

Author: rovka Date: Wed Jan 25 00:23:50 2017 New Revision: 293026 URL: http://llvm.org/viewvc/llvm-project?rev=293026=rev Log: Try to fix test from r293004 This test broke on a lot of non-x86 buildbots with "unknowm CPU" errors. I don't see anything platform-specific about this test, and it

Re: r286098 - [OPENMP] Fixed capturing of VLA variables.

Hi Alexey, If it is not a simple, quick fix that you can do, it is customary to revert so the buildbots become green again. Otherwise, if people commit other things that break the build they will not get emails and it will be much harder to fix the whole thing. I'll revert this for you and you

r286102 - Revert "[OPENMP] Fixed capturing of VLA variables."

Author: rovka Date: Mon Nov 7 04:01:43 2016 New Revision: 286102 URL: http://llvm.org/viewvc/llvm-project?rev=286102=rev Log: Revert "[OPENMP] Fixed capturing of VLA variables." This reverts commit r286098 because the modified test breaks on many of the buildbots. Modified:

Re: r286098 - [OPENMP] Fixed capturing of VLA variables.

Hi, This has been breaking the bots for almost an hour. Can you fix/revert? http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/304 http://lab.llvm.org:8011/builders/clang-hexagon-elf/builds/657 http://lab.llvm.org:8011/builders/clang-x86-windows-msvc2015/builds/347 Thanks, Diana On

Re: [PATCH] D24245: [ARM] ARM-specific attributes should be accepted for big-endian

rovka added a subscriber: rovka. rovka accepted this revision. rovka added a reviewer: rovka. rovka added a comment. This revision is now accepted and ready to land. Looks like a sensible thing to do. Repository: rL LLVM https://reviews.llvm.org/D24245

Re: r280575 - Add plumbing for new attribute type "Microsoft".

Scratch that, apparently it fixed itself after I removed the build directory and restarted the bot. Sorry about the noise. Diana On 7 September 2016 at 11:10, Diana Picus wrote: > Hi Nico, > > One of our thumb bots [1] is having issues building lately and it > looks like

Re: r280575 - Add plumbing for new attribute type "Microsoft".

Hi Nico, One of our thumb bots [1] is having issues building lately and it looks like it might be related to one of the commits in this series. Could you please have a look? Thanks, Diana [1]

Re: [PATCH] D23528: [OpenMP] Sema and parsing for 'teams distribute simd' pragma

Hi, I had to revert this (r279045) because it breaks some of our buildbots (e.g. clang-cmake-aarch64-quick, clang-x86_64-linux-selfhost-modules). The error is in OpenMP/teams_distribute_simd_ast_print.cpp: clang:

Re: [PATCH] D22904: Fix two bugs for musl-libc on ARM

rovka added a subscriber: rovka. rovka added a comment. Hi Lei, Renato is on vacation, so I committed this for you. Regards, Diana Repository: rL LLVM https://reviews.llvm.org/D22904 ___ cfe-commits mailing list cfe-commits@lists.llvm.org

Re: [PATCH] D22904: Fix two bugs for musl-libc on ARM

This revision was automatically updated to reflect the committed changes. Closed by commit rL277985: Fix two bugs for musl-libc on ARM (authored by rovka). Changed prior to commit: https://reviews.llvm.org/D22904?vs=66074=67131#toc Repository: rL LLVM https://reviews.llvm.org/D22904

r277985 - Fix two bugs for musl-libc on ARM

Author: rovka Date: Mon Aug 8 03:27:36 2016 New Revision: 277985 URL: http://llvm.org/viewvc/llvm-project?rev=277985=rev Log: Fix two bugs for musl-libc on ARM Bug 1: triples like armv7-pc-linux-musl use the wrong linker name ld-musl-armv7.so.1; the right name should be ld-musl-arm.so.1,

Re: [PATCH] D23054: [clang-cl] Fix PCH tests to use x86_64 as target

This revision was automatically updated to reflect the committed changes. Closed by commit rL277457: [clang-cl] Fix PCH tests to use x86_64 as target (authored by rovka). Changed prior to commit: https://reviews.llvm.org/D23054?vs=66467=66468#toc Repository: rL LLVM

r277457 - [clang-cl] Fix PCH tests to use x86_64 as target

Author: rovka Date: Tue Aug 2 08:53:00 2016 New Revision: 277457 URL: http://llvm.org/viewvc/llvm-project?rev=277457=rev Log: [clang-cl] Fix PCH tests to use x86_64 as target These tests require x86-registered-target, but they don't force the target as x86 on the command line, which means they

Re: [PATCH] D23054: [clang-cl] Fix PCH tests to use x86_64 as target

rovka retitled this revision from "[clang-cl] Fix 2 pch tests to use x86_64 as target" to "[clang-cl] Fix PCH tests to use x86_64 as target". rovka updated this revision to Diff 66467. rovka added a comment. Added cl-pch-errorhandling.cpp https://reviews.llvm.org/D23054 Files:

Re: [PATCH] D23054: [clang-cl] Fix 2 pch tests to use x86_64 as target

rovka added a comment. In https://reviews.llvm.org/D23054#503246, @rengolin wrote: > All tests should have the target explicit, so I'd advocate for all of them to > be changed. Coming right up... > Also, we need to make sure --target=x86_64 is enough on Windows. I remember > some

Re: [PATCH] D23054: [clang-cl] Fix 2 pch tests to use x86_64 as target

rovka added a comment. This seems to be the case for other similar tests as well (e.g. cl-pch-errorhandling.cpp requires x86-registered-target, but doesn't force it on the command line), but they're not currently crashing. I can update those as well if people think it's the right thing to do.

[PATCH] D23054: [clang-cl] Fix 2 pch tests to use x86_64 as target

rovka created this revision. rovka added a reviewer: thakis. rovka added subscribers: cfe-commits, hans. Herald added a subscriber: aemerson. These tests require x86-registered-target, but they don't force the target as x86 on the command line, which means they will be run and they might fail

Re: [libcxx] r274605 - Fix typo in #ifdef, and re-enable tests now that the green-dragon bots are no more

Hi Marhsall, This seems to be breaking our libcxx bot: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-arm-linux/builds/1126 I'm a bit confused by that comment you removed, do we need to update our bot in any way? Thanks, Diana On 6 July 2016 at 08:28, Marshall Clow via cfe-commits

Re: [PATCH] D20157: Add test for D20156

rovka abandoned this revision. rovka added a comment. With the new diagnostic handler in r269428, we no longer need this test (it will be covered by the existing tests such as CodeGen/AArch64/arm64-inline-asm-error-N.ll, by removing the -exit-on-error flag). http://reviews.llvm.org/D20157

[PATCH] D20157: Add test for D20156

rovka created this revision. rovka added reviewers: rengolin, resistor, mcrosier, echristo, qcolombet, bogner. rovka added subscribers: llvm-commits, cfe-commits. Herald added a subscriber: joker.eph. This adds a test for PR24071. Its purpose is to make sure that we do not assert after

Re: r267866 - [MS] Improved implementation of MS stack pragmas (vtordisp, *_seg)

Hi, I don't know if you've noticed, but this commit broke a lot of builds - e.g. http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15/builds/11865. Regards, Diana On 28 April 2016 at 13:13, Denis Zobnin via cfe-commits < cfe-commits@lists.llvm.org> wrote: > Author: dzobnin > Date: Thu Apr