RichardLuo0 wrote:
> Is there a similar change that is proposed for the main branch?
Yes https://github.com/llvm/llvm-project/pull/91240, I forget to mention that
here.
https://github.com/llvm/llvm-project/pull/91182
___
llvm-branch-commits mailing
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/91906
>From 972047a832f4fe67170f08f4f75bd3c0bb614021 Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Sun, 12 May 2024 17:37:48 -0700
Subject: [PATCH 1/2] fix test
Created using spr 1.3.4
---
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/91906
>From 972047a832f4fe67170f08f4f75bd3c0bb614021 Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Sun, 12 May 2024 17:37:48 -0700
Subject: [PATCH 1/2] fix test
Created using spr 1.3.4
---
https://github.com/aaupov edited https://github.com/llvm/llvm-project/pull/92017
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/92017
>From 096f5cc4cae69a428629a8c05f5e4ce373ca7d60 Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Thu, 16 May 2024 23:00:50 -0400
Subject: [PATCH] TakenBranchInfo
Created using spr 1.3.5
---
Author: Jonas Devlieghere
Date: 2024-05-16T19:58:44-07:00
New Revision: ebb9f82e4c6f9b7c6f627da71ffbfb858f655d1e
URL:
https://github.com/llvm/llvm-project/commit/ebb9f82e4c6f9b7c6f627da71ffbfb858f655d1e
DIFF:
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/92017
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/92017
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-llvm-transforms
Author: AtariDreams (AtariDreams)
Changes
This was looking through an addrspacecast, and not finding a later unfoldable
cast to another address space. Fixes improperly deleting a required alloca +
memcpy and introducing an illegal
https://github.com/AtariDreams created
https://github.com/llvm/llvm-project/pull/92479
This was looking through an addrspacecast, and not finding a later unfoldable
cast to another address space. Fixes improperly deleting a required alloca +
memcpy and introducing an illegal addrspacecast.
llvmbot wrote:
@llvm/pr-subscribers-lld-macho
Author: AtariDreams (AtariDreams)
Changes
When -ObjC is passed, the linker must force load any object files that contain
special sections that store Objective-C / Swift information that is used at
runtime.
This should work regadless if
https://github.com/AtariDreams updated
https://github.com/llvm/llvm-project/pull/92478
>From 8c9c7a49a36eccaca8867b2535988cf12ba6b41d Mon Sep 17 00:00:00 2001
From: Nuri Amari
Date: Wed, 15 May 2024 09:21:02 -0700
Subject: [PATCH] [lld] Fix -ObjC load behavior with LTO (#92162)
When -ObjC is
https://github.com/AtariDreams created
https://github.com/llvm/llvm-project/pull/92478
When -ObjC is passed, the linker must force load any object files that contain
special sections that store Objective-C / Swift information that is used at
runtime.
This should work regadless if input files
https://github.com/wangleiat updated
https://github.com/llvm/llvm-project/pull/92376
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangleiat updated
https://github.com/llvm/llvm-project/pull/92376
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangleiat updated
https://github.com/llvm/llvm-project/pull/92375
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangleiat updated
https://github.com/llvm/llvm-project/pull/92375
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
DianQK wrote:
Per https://github.com/llvm/llvm-project/pull/91483#issuecomment-2116394616, we
still need to further investigate this issue, but it won't stop us from
backporting it.
cc @MaskRay
https://github.com/llvm/llvm-project/pull/92468
___
DianQK wrote:
Release note (maybe):
Do not replace an aliasee with an alias that has weak linkage, as this prevents
the selection of incorrect symbols during the linking time.
@tstellar
https://github.com/llvm/llvm-project/pull/92468
___
DianQK wrote:
> As noted on the original pull request, this also affects some cases which
> might be safe to optimize (a weak alias where the aliasee is an internal
> symbol with no other references). But "optimizing" those cases doesn't really
> have any useful effect, anyway: it doesn't
https://github.com/efriedma-quic approved this pull request.
LGTM
This only affects optimizations on weak aliases, and the logic is very simple:
just don't optimize them.
As noted on the original pull request, this also affects some cases which might
be safe to optimize (a weak alias where
llvmbot wrote:
@llvm/pr-subscribers-llvm-transforms
Author: None (llvmbot)
Changes
Backport c79690040acf5bb3d857558b0878db47f7f23dc3
Requested by: @DianQK
---
Full diff: https://github.com/llvm/llvm-project/pull/92468.diff
2 Files Affected:
- (modified)
llvmbot wrote:
@efriedma-quic What do you think about merging this PR to the release branch?
https://github.com/llvm/llvm-project/pull/92468
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://github.com/llvmbot milestoned
https://github.com/llvm/llvm-project/pull/92468
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/llvmbot created
https://github.com/llvm/llvm-project/pull/92468
Backport c79690040acf5bb3d857558b0878db47f7f23dc3
Requested by: @DianQK
>From 012e13b1594ba19058294d793993ad8da14c9159 Mon Sep 17 00:00:00 2001
From: DianQK
Date: Fri, 17 May 2024 05:51:49 +0800
Subject:
https://github.com/asb approved this pull request.
https://github.com/llvm/llvm-project/pull/92143
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
asb wrote:
My thoughts:
* Thanks to @negge and others for clarifying who this is affecting and how
* It's very unfortunate we've broken some use cases here. Though as, by my
understand, this is affecting people using internal flags as opposed to
documented top-level flags I feel there's not a
tstellar wrote:
@topperc The plan is to release Friday. Do we have agreement on merging this
updated patch?
https://github.com/llvm/llvm-project/pull/92143
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
topperc wrote:
> @topperc Can this be merged as is? There might not be time to get an updated
> patch merged before the last release.
I just pushed a modified patch. What is the timeline for the last release?
https://github.com/llvm/llvm-project/pull/92143
https://github.com/topperc edited
https://github.com/llvm/llvm-project/pull/92143
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/topperc updated
https://github.com/llvm/llvm-project/pull/92143
>From e18e442947da7801c915c04e34e397464eca5034 Mon Sep 17 00:00:00 2001
From: Craig Topper
Date: Thu, 16 May 2024 12:27:05 -0700
Subject: [PATCH] [RISCV] Add a unaligned-scalar-mem feature like we had in
clang
tstellar wrote:
Is there a similar change that is proposed for the main branch?
https://github.com/llvm/llvm-project/pull/91182
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
tstellar wrote:
@topperc Can this be merged as is? There might not be time to get an updated
patch merged before the last release.
https://github.com/llvm/llvm-project/pull/92143
___
llvm-branch-commits mailing list
tstellar wrote:
@dtcxzyw (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.
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/91917
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: Tom Stellard
Date: 2024-05-16T11:42:50-07:00
New Revision: 2a4a0bf1db8b828f104123de52d9f9cace020ed0
URL:
https://github.com/llvm/llvm-project/commit/2a4a0bf1db8b828f104123de52d9f9cace020ed0
DIFF:
https://github.com/llvm/llvm-project/commit/2a4a0bf1db8b828f104123de52d9f9cace020ed0.diff
Author: Yingwei Zheng
Date: 2024-05-16T11:42:50-07:00
New Revision: 26ccc6b5c1c73a92e5d08299065709e1d163b6c2
URL:
https://github.com/llvm/llvm-project/commit/26ccc6b5c1c73a92e5d08299065709e1d163b6c2
DIFF:
https://github.com/llvm/llvm-project/commit/26ccc6b5c1c73a92e5d08299065709e1d163b6c2.diff
topperc wrote:
> I'm not strongly opposed to this or anything, but it feels questionable to be
> doing a backport to change the target-feature syntax. My understand is that
> these are purely internal names. This isn't a documented public interface.
It isn't documented, but some users were
preames wrote:
I'm not strongly opposed to this or anything, but it feels questionable to be
doing a backport to change the target-feature syntax. My understand is that
these are purely internal names. This isn't a documented public interface.
negge wrote:
I can confirm that bus error on unaligned vector access also happens on the
recently released Banana Pi BPI-F3 when using clang-18.1.5.
Note the BPI-F3 (https://docs.banana-pi.org/en/BPI-F3/BananaPi_BPI-F3) is a
different SOC from the K230 and right now these are the only two
https://github.com/SixWeining approved this pull request.
https://github.com/llvm/llvm-project/pull/92376
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/SixWeining approved this pull request.
LGTM. I think this fix should be check-picked to 18.x.
https://github.com/llvm/llvm-project/pull/92375
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://github.com/heiher approved this pull request.
https://github.com/llvm/llvm-project/pull/92376
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/heiher approved this pull request.
https://github.com/llvm/llvm-project/pull/92375
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
Author: wanglei (wangleiat)
Changes
The 32 bits arguments and returns on LA64 are always sign extended to
i64. So we should be taking this into account around libcalls.
---
Full diff:
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
Author: wanglei (wangleiat)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/92376.diff
7 Files Affected:
- (modified) llvm/lib/Target/LoongArch/LoongArchISelLowering.cpp (+9)
- (modified)
https://github.com/wangleiat created
https://github.com/llvm/llvm-project/pull/92376
None
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangleiat created
https://github.com/llvm/llvm-project/pull/92375
The 32 bits arguments and returns on LA64 are always sign extended to
i64. So we should be taking this into account around libcalls.
___
llvm-branch-commits
https://github.com/xen0n approved this pull request.
https://github.com/llvm/llvm-project/pull/92223
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/SixWeining approved this pull request.
https://github.com/llvm/llvm-project/pull/92223
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangleiat updated
https://github.com/llvm/llvm-project/pull/92223
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangleiat updated
https://github.com/llvm/llvm-project/pull/92223
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -49,63 +50,127 @@ static ABI checkABIStandardized(ABI Abi) {
return Abi;
}
-ABI computeTargetABI(const Triple , StringRef ABIName) {
- ABI ArgProvidedABI = getTargetABI(ABIName);
+static ABI getTripleABI(const Triple ) {
bool Is64Bit = TT.isArch64Bit();
ABI
53 matches
Mail list logo
