[llvm-branch-commits] [clang] [CIR] Untie Type and Attribute definitions (PR #146663)

2025-07-02 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper approved this pull request. https://github.com/llvm/llvm-project/pull/146663 ___ 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] [clang] [CIR] Clean up FPAttr (PR #146662)

2025-07-02 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper approved this pull request. https://github.com/llvm/llvm-project/pull/146662 ___ 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] [clang] [CIR] Upstream __real__ for ComplexType (PR #144261)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper ready_for_review https://github.com/llvm/llvm-project/pull/144261 ___ 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] [clang] [CIR] Upstream __imag__ for ComplexType (PR #144262)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper ready_for_review https://github.com/llvm/llvm-project/pull/144262 ___ 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] [clang] [CIR] Upstream __imag__ for ComplexType (PR #144262)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper edited https://github.com/llvm/llvm-project/pull/144262 ___ 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] [clang] [CIR] Upstream __real__ for ComplexType (PR #144261)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper edited https://github.com/llvm/llvm-project/pull/144261 ___ 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] [clang] [CIR] Upstream __imag__ for ComplexType (PR #144262)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper edited https://github.com/llvm/llvm-project/pull/144262 ___ 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] [clang] [CIR] Upstream __imag__ for ComplexType (PR #144262)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
AmrDeveloper wrote: > [!WARNING] > This pull request is not mergeable via GitHub because a downstack PR is > open. Once all requirements are satisfied, merge this PR as a stack href="https://app.graphite.dev/github/pr/llvm/llvm-project/144262?utm_source=stack-comment-downstack-mergeability-warn

[llvm-branch-commits] [clang] [CIR] Upstream __real__ for ComplexType (PR #144261)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
AmrDeveloper wrote: > [!WARNING] > This pull request is not mergeable via GitHub because a downstack PR is > open. Once all requirements are satisfied, merge this PR as a stack href="https://app.graphite.dev/github/pr/llvm/llvm-project/144261?utm_source=stack-comment-downstack-mergeability-warn

[llvm-branch-commits] [clang] [CIR] Upstream __real__ for ComplexType (PR #144261)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper created https://github.com/llvm/llvm-project/pull/144261 None >From 9cbbfd20f045ca71e51d5bddd5e2bbe5a8ddd22f Mon Sep 17 00:00:00 2001 From: AmrDeveloper Date: Sun, 15 Jun 2025 14:44:11 +0200 Subject: [PATCH] [CIR] Upstream __real__ for ComplexType --- clang/li

[llvm-branch-commits] [clang] [CIR] Upstream __imag__ for ComplexType (PR #144262)

2025-06-15 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper created https://github.com/llvm/llvm-project/pull/144262 None >From fa6756886c5e0d432445d2364d92ff38ad0127ae Mon Sep 17 00:00:00 2001 From: AmrDeveloper Date: Sun, 15 Jun 2025 14:45:12 +0200 Subject: [PATCH] [CIR] Upstream __imag__ for ComplexType --- clang/li

[llvm-branch-commits] [clang] [CIR] Upstream ComplexImagPtrOp for ComplexType (PR #144236)

2025-06-14 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper edited https://github.com/llvm/llvm-project/pull/144236 ___ 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] [clang] [CIR] Upstream ComplexImagPtrOp for ComplexType (PR #144236)

2025-06-14 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper ready_for_review https://github.com/llvm/llvm-project/pull/144236 ___ 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] [clang] [CIR] Upstream ComplexImagPtrOp for ComplexType (PR #144236)

2025-06-14 Thread Amr Hesham via llvm-branch-commits
AmrDeveloper wrote: > [!WARNING] > This pull request is not mergeable via GitHub because a downstack PR is > open. Once all requirements are satisfied, merge this PR as a stack href="https://app.graphite.dev/github/pr/llvm/llvm-project/144236?utm_source=stack-comment-downstack-mergeability-warn

[llvm-branch-commits] [clang] [CIR] Upstream ComplexImagPtrOp for ComplexType (PR #144236)

2025-06-14 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper created https://github.com/llvm/llvm-project/pull/144236 None >From dc824e4ff23a7ff5124de5a21362e5b543c55d27 Mon Sep 17 00:00:00 2001 From: AmrDeveloper Date: Sat, 14 Jun 2025 22:19:08 +0200 Subject: [PATCH] [CIR] Upstream ComplexImagPtrOp for ComplexType ---

[llvm-branch-commits] [llvm] release/20.x: [llvm-objcopy][ReleaseNotes] Fix prints wrong path when dump-section output path doesn't exist #125345 (PR #126607)

2025-02-11 Thread Amr Hesham via llvm-branch-commits
@@ -460,6 +460,8 @@ Changes to the LLVM tools `--localize-symbol`, `--localize-symbols`, `--skip-symbol`, `--skip-symbols`. +* llvm-objcopy now prints the correct file path in the error message when the output file specified by --dump-section cannot be opened. ---

[llvm-branch-commits] [llvm] release/20.x: [llvm-objcopy][ReleaseNotes] Fix prints wrong path when dump-section output path doesn't exist #125345 (PR #126607)

2025-02-11 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper updated https://github.com/llvm/llvm-project/pull/126607 >From 8886b33981f73da04adadb3e02a740b8e376e042 Mon Sep 17 00:00:00 2001 From: AmrDeveloper Date: Mon, 10 Feb 2025 23:03:15 +0100 Subject: [PATCH 1/2] release/20.x: [llvm-objcopy][ReleaseNotes] Fix prints w

[llvm-branch-commits] [llvm] release/20.x: [llvm-objcopy][ReleaseNotes] Fix prints wrong path when dump-section output path doesn't exist #125345 (PR #126607)

2025-02-10 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper created https://github.com/llvm/llvm-project/pull/126607 Add release note for llvm-objcopy fixing prints wrong path when dump-section output path doesn't exist in #125345 >From 8886b33981f73da04adadb3e02a740b8e376e042 Mon Sep 17 00:00:00 2001 From: AmrDeveloper

[llvm-branch-commits] [llvm] release/20.x: [llvm-objcopy] Fix prints wrong path when dump-section output path doesn't exist (#125345) (PR #126367)

2025-02-10 Thread Amr Hesham via llvm-branch-commits
https://github.com/AmrDeveloper approved this pull request. https://github.com/llvm/llvm-project/pull/126367 ___ 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/20.x: [llvm-objcopy] Fix prints wrong path when dump-section output path doesn't exist (#125345) (PR #126367)

2025-02-10 Thread Amr Hesham via llvm-branch-commits
AmrDeveloper wrote: > LGTM. > > Regarding the release note, you'll need one on the release branch. IIUC, you > won't then need one on `main`, because the release branch is still in RC > mode, so not a final release yet. Not sure if I can push release note on this PR only, but I will create a