[llvm-branch-commits] [llvm] release/20.x: [IR] Fix assertion error in User new/delete edge case (#129914) (PR #130580)

marcauberer wrote: > @marcauberer (or anyone else). If you would like to add a note about this fix > in the release notes (completely optional). Please reply to this comment with > a one or two sentence description of the fix. When you are done, please add > the release:note label to this PR.

[llvm-branch-commits] [llvm] release/20.x: [IR] Fix assertion error in User new/delete edge case (#129914) (PR #130580)

https://github.com/marcauberer updated https://github.com/llvm/llvm-project/pull/130580 >From b3515aa07b42164268a835e3f5874f49056a2e22 Mon Sep 17 00:00:00 2001 From: Marc Auberer Date: Mon, 10 Mar 2025 11:53:45 +0100 Subject: [PATCH] [IR] Fix assertion error in User new/delete edge case (#1299

[llvm-branch-commits] [llvm] release/18.x: [AArch64][GISEL] Consider fcmp true and fcmp false in cond code selection (#86972) (PR #91126)

marcauberer wrote: @tstellar yes, see https://github.com/llvm/llvm-project/pull/91580 https://github.com/llvm/llvm-project/pull/91126 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinf

[llvm-branch-commits] [llvm] release/18.x: [AArch64][GISEL] Consider fcmp true and fcmp false in cond code selection (#86972) (PR #91580)

marcauberer wrote: @tstellar Fixes crash in AArch64 backend when having `true` or `false` as operand for a fcmp instruction on IR level. https://github.com/llvm/llvm-project/pull/91580 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llv

[llvm-branch-commits] [llvm] release/18.x: [AArch64][GISEL] Consider fcmp true and fcmp false in cond code selection (#86972) (PR #91126)

https://github.com/marcauberer closed https://github.com/llvm/llvm-project/pull/91126 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [llvm] release/18.x: [AArch64][GISEL] Consider fcmp true and fcmp false in cond code selection (#86972) (PR #91580)

https://github.com/marcauberer milestoned https://github.com/llvm/llvm-project/pull/91580 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [llvm] release/18.x: [AArch64][GISEL] Consider fcmp true and fcmp false in cond code selection (#86972) (PR #91580)

https://github.com/marcauberer created https://github.com/llvm/llvm-project/pull/91580 Backport c482fad2c1de367f8fef2b40361dec00523707f7 This cherry-pick includes some ref fixes due to the incompatibility between `main` and `release/18.x`. >From 39f3ca9677a63ddc404e7ee13edace2bbf72fc93 Mon Se

[llvm-branch-commits] [llvm] release/18.x: [AArch64][GISEL] Consider fcmp true and fcmp false in cond code selection (#86972) (PR #91126)

marcauberer wrote: @arsenm How are lit test failures handled in case of cherry-picks? Seems like GISEL behaves a bit different on `release/18.x`. I have a fix prepared locally, but how should I push it? I can't push to a llvmbot branch, can I? https://github.com/llvm/llvm-project/pull/91126 __