[llvm-branch-commits] [llvm] release/20.x: [HEXAGON] Fix corner cases for hwloops pass (#135439) (PR #135657)

androm3da wrote: @iajbar, please review. https://github.com/llvm/llvm-project/pull/135657 ___ 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][CodeGen] avoid repeated interval calculation in window scheduler (#132352) (PR #134775)

androm3da wrote: @huatian can you review this cherry-pick? https://github.com/llvm/llvm-project/pull/134775 ___ 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: [HEXAGON] Fix semantics of ordered FP compares (#131089) (PR #131270)

androm3da wrote: @iajbar can you review the cherry-pick of this floating point comparison fix? https://github.com/llvm/llvm-project/pull/131270 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailm

[llvm-branch-commits] [clang] release/20.x: [hexagon] Enable --eh-frame-hdr (#130225) (PR #130678)

androm3da wrote: @iajbar can you review this cherry-pick for the compiler driver? https://github.com/llvm/llvm-project/pull/130678 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/

[llvm-branch-commits] [clang] [llvm] release/20.x: [Hexagon] Set the default compilation target to V68 (#125239) (PR #128597)

androm3da wrote: /cherry-pick 759ef5811e22 c0b2c10e9f3a https://github.com/llvm/llvm-project/pull/128597 ___ 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] [llvm] release/20.x: [Hexagon] Set the default compilation target to V68 (#125239) (PR #128597)

androm3da wrote: /cherry-pick 759ef5811e22 1abe7e8debc44d9a7e460c2be0b85b7cf137585b c0b2c10e9f3a https://github.com/llvm/llvm-project/pull/128597 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/ma

[llvm-branch-commits] [llvm] release/20.x: [hexagon] Prevent alignment search beyond a label (#130631) (PR #132336)

https://github.com/androm3da approved this pull request. https://github.com/llvm/llvm-project/pull/132336 ___ 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: [HEXAGON] Add support to lower "FREEZE a half(f16)" instruction on Hexagon and fix the isel-buildvector-v2f16.ll assertion (#130977) (PR #132138)

https://github.com/androm3da approved this pull request. Assuming it's safe to define a new override for `softPromoteHalfType()` in a new 20.x release, this LGTM. https://github.com/llvm/llvm-project/pull/132138 ___ llvm-branch-commits mailing list ll

[llvm-branch-commits] [clang] [llvm] release/20.x: [Hexagon] Set the default compilation target to V68 (#125239) (PR #128597)

androm3da wrote: @quic-akaryaki can you fix #127558 on `main` and then cherry-pick it to 20.x? Because we are going to hold this pull req from 20.x until that one is ready. Or at least IMO it doesn't make sense to change the default compiler target without also changing the default for the a

[llvm-branch-commits] [llvm] release/20.x: [Hexagon] Handle Call Operand vxi1 in Hexagon Backend (#128027) (PR #129311)

androm3da wrote: > > Does this need to be in 20.1.0 or could it wait until 20.1.1 ? > > It can wait. Hmm -- or, rather -- I should ask @alexrp whether it can wait. https://github.com/llvm/llvm-project/pull/129311 ___ llvm-branch-commits mailing list

[llvm-branch-commits] [llvm] release/20.x: [Hexagon] Handle Call Operand vxi1 in Hexagon Backend (#128027) (PR #129311)

androm3da wrote: > Does this need to be in 20.1.0 or could it wait until 20.1.1 ? It can wait. https://github.com/llvm/llvm-project/pull/129311 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mail

[llvm-branch-commits] [llvm] release/20.x: [Hexagon] Add a case to BitTracker for new register class (#128580) (PR #128738)

androm3da wrote: > @androm3da What do you think about merging this PR to the release branch? well I just love that idea, tyvm @llvmbot https://github.com/llvm/llvm-project/pull/128738 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llv

[llvm-branch-commits] [llvm] release/20.x: [Hexagon] Add a case to BitTracker for new register class (#128580) (PR #128738)

https://github.com/androm3da approved this pull request. https://github.com/llvm/llvm-project/pull/128738 ___ 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] [llvm] release/20.x: [Hexagon] Set the default compilation target to V68 (#125239) (PR #128597)

androm3da wrote: > > @smithp35 @jh7370 @androm3da What do you think about backporting this? > > sounds good - but if we make this change we should also make sure #127558 is > fixed and backported. @quic-akaryaki is that something you think you'll be > able to address? If not, I can take a look

[llvm-branch-commits] [clang] [llvm] release/20.x: [Hexagon] Set the default compilation target to V68 (#125239) (PR #128597)

androm3da wrote: > @smithp35 @jh7370 @androm3da What do you think about backporting this? sounds good - but if we make this change we should also make sure #127558 is fixed and backported. @quic-akaryaki is that something you think you'll be able to address? If not, I can take a look. https

[llvm-branch-commits] [llvm] release/19.x: [Hexagon] Only handle simple types memory accesses (#120654) (PR #121061)

https://github.com/androm3da approved this pull request. https://github.com/llvm/llvm-project/pull/121061 ___ 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] release/19.x: [clang] recognize hexagon-*-ld.lld variants (#117338) (PR #118181)

androm3da wrote: ping @MaskRay https://github.com/llvm/llvm-project/pull/118181 ___ 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] [lld] [lld][Hexagon] Fix R_HEX_B22_PCREL range checks (#115925) (PR #116906)

https://github.com/androm3da milestoned https://github.com/llvm/llvm-project/pull/116906 ___ 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] [lld] [lld][Hexagon] Fix R_HEX_B22_PCREL range checks (#115925) (PR #116906)

androm3da wrote: Fixes #116798 https://github.com/llvm/llvm-project/pull/116906 ___ 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] [lld] [lld][Hexagon] Fix R_HEX_B22_PCREL range checks (#115925) (PR #116906)

https://github.com/androm3da created https://github.com/llvm/llvm-project/pull/116906 Range checks for R_HEX_B22_PCREL did not account for the fact that offset is measured in instructions, not bytes. Add a test for all range-checked relocations. >From 6a1fd8a3eca7e4992d5053c18f3b3ef57bf2503c

[llvm-branch-commits] [libcxx] release/19.x: [libc++] Use a different smart ptr type alias (#102089) (PR #103003)

https://github.com/androm3da updated https://github.com/llvm/llvm-project/pull/103003 >From 2188e4b6b6dc257436f6d9086fe0b7205f8d512a Mon Sep 17 00:00:00 2001 From: Brian Cain Date: Mon, 12 Aug 2024 20:07:08 -0500 Subject: [PATCH] [libc++] Use a different smart ptr type alias (#102089) The `_SP

[llvm-branch-commits] [libcxx] release/18.x: [libcxx] coerce formatter precision to int (#87738) (PR #87801)

androm3da wrote: I think omitting this from the release notes makes sense. https://github.com/llvm/llvm-project/pull/87801 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bra

[llvm-branch-commits] [libcxx] release/18.x: [libcxx] coerce formatter precision to int (#87738) (PR #87801)

androm3da wrote: > Is it OK to merge this with the failing test? is it possible this was a fix for an XFAIL @mordante ? https://github.com/llvm/llvm-project/pull/87801 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lis