https://github.com/yxsamliu closed
https://github.com/llvm/llvm-project/pull/133590
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-aarch64-ubuntu`
running on `linaro-lldb-aarch64-ubuntu` while building `clang` at step 6 "test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/59/builds/15227
Here is the relevant piece of the
https://github.com/Artem-B approved this pull request.
https://github.com/llvm/llvm-project/pull/133590
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/yxsamliu updated
https://github.com/llvm/llvm-project/pull/133590
>From 3f533ad3a54b199e96a14e91f01b9714c30f52c2 Mon Sep 17 00:00:00 2001
From: "Yaxun (Sam) Liu"
Date: Sun, 25 Feb 2024 11:13:40 -0500
Subject: [PATCH] [HIP] fix host min/max in header
CUDA defines min/max func
llvmbot wrote:
@llvm/pr-subscribers-backend-x86
Author: Yaxun (Sam) Liu (yxsamliu)
Changes
CUDA defines min/max functions for host in global namespace. HIP header needs
to define them too to be compatible. Currently only min/max(int, int) is
defined. This causes wrong result for argument
yxsamliu wrote:
This is an effort to reland https://github.com/llvm/llvm-project/pull/82956
Since we kept encountering regressions, we plan to add the change conditionally
under a macro so that we can deliver the fix to intended users without causing
regressions. Then we will try making the ch
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Yaxun (Sam) Liu (yxsamliu)
Changes
CUDA defines min/max functions for host in global namespace. HIP header needs
to define them too to be compatible. Currently only min/max(int, int) is
defined. This causes wrong result for arguments that
https://github.com/yxsamliu created
https://github.com/llvm/llvm-project/pull/133590
CUDA defines min/max functions for host in global namespace. HIP header needs
to define them too to be compatible. Currently only min/max(int, int) is
defined. This causes wrong result for arguments that are o
