summary |
shortlog | log |
commit |
commitdiff |
tree
first ⋅ prev ⋅ next
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
arm
===================================================================
Gbp-Pq: Name 930008-arm.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
hurd-f_type
https://github.com/llvm/llvm-project/pull/71851
commit
620b8d994b8abdcf31271d9f4db7e7422fc9bd65
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Mon Sep 9 15:53:33 2024 +0200
[hurd] Fix accessing f_type field of statvfs (#71851)
f4719c4d2cda ("Add support for GNU Hurd in Path.inc and other places")
made llvm use an internal __f_type name for the f_type field (which it
is not supposed to since accessing double-underscore names is explicitly
not supported by standards). In glibc 2.39 this field was renamed to
f_type so application can now access the field as the standard says.
Gbp-Pq: Topic hurd
Gbp-Pq: Name hurd-f_type.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
hurd-pathmax
===================================================================
Gbp-Pq: Topic hurd
Gbp-Pq: Name hurd-pathmax.diff
Nicholas D Steeves [Sun, 11 Feb 2018 02:02:17 +0000 (21:02 -0500)]
Use Debian-provided MathJax everywhere.
Gbp-Pq: Name 0049-Use-Debian-provided-MathJax-everywhere.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
remove-apple-clang-manpage
===================================================================
Gbp-Pq: Name remove-apple-clang-manpage.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
clangd-atomic-cmake
===================================================================
Gbp-Pq: Name clangd-atomic-cmake.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
clang-arm-default-vfp3-on-armv7a
===================================================================
Gbp-Pq: Name clang-arm-default-vfp3-on-armv7a.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
disable-sse2-old-x86
===================================================================
Gbp-Pq: Name disable-sse2-old-x86.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
clang-baseline-fix-i386
===================================================================
Gbp-Pq: Name clang-baseline-fix-i386.patch
Peter Michael Green [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
set correct float abi settings for armel and armhf
debian armel supports systems that don't have a fpu so should use a "float abi"
setting of soft by default.
Debian armhf needs a float abi setting of "hard"
Gbp-Pq: Name 26-set-correct-float-abi.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
syscall-mips64el-def
===================================================================
Gbp-Pq: Topic mips
Gbp-Pq: Name syscall-mips64el-def.diff
Dimitry Andric [Mon, 3 May 2021 18:08:49 +0000 (20:08 +0200)]
[PATCH] [MC][ELF] Work around R_MIPS_LO16 relocation handling problem
This fixes PR49821, and avoids "ld.lld: error: test.o:(.rodata.str1.1):
offset is outside the section" errors when linking MIPS objects with
negative R_MIPS_LO16 implicit addends.
ld.lld handles R_MIPS_HI16/R_MIPS_LO16 separately, not as a whole, so it
doesn't know that an R_MIPS_HI16 with implicit addend 1 and an
R_MIPS_LO16 with implicit addend -32768 represents 32768, which is in
range of a MergeInputSection. We could introduce a new RelExpr member
(like R_RISCV_PC_INDIRECT for R_RISCV_PCREL_HI20 / R_RISCV_PCREL_LO12)
but the complexity is unnecessary given that GNU as keeps the original
symbol for this case as well.
Reviewed By: atanasyan, MaskRay
Differential Revision: https://reviews.llvm.org/
D101773
Gbp-Pq: Topic mips
Gbp-Pq: Name mips-
D101773-reloc.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
mips-force-nomadd4
The MIPS port aims to support the Loongson 3 family of CPUs in addition
of the other MIPS CPUs. On the Loongson 3 family the MADD4 instructions
are fused, while they are not fused on the other MIPS CPUs. In order to
support both, we have to disabled those instructions.
For that, the patch below basically corresponds to the --with-madd4=no
used on the GCC side.
Gbp-Pq: Topic mips
Gbp-Pq: Name mips-force-nomadd4.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
mips-fpxx-enable
===================================================================
Gbp-Pq: Topic mips
Gbp-Pq: Name mips-fpxx-enable.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxx-armhf-ftbfs
===================================================================
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxx-armhf-ftbfs.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxxabi-fix-link-builtins
if LIBCXXABI_USE_COMPILER_RT=ON, add builtins to libcxxabi library
flags, otherwise add libgcc following how libunwind does the same
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxxabi-fix-link-builtins.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxx-libatomic-only-with-gcc-rtlib
if libatomic is found only link it if libgcc is the rtlib
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxx-libatomic-only-with-gcc-rtlib.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxx-silent-failure-arm64
===================================================================
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxx-silent-failure-arm64.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxx-silent-failure-ppc64el
===================================================================
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxx-silent-failure-ppc64el.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxx-silent-test-libcxx
===================================================================
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxx-silent-test-libcxx.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxxabi-arm-ehabi-fix
Fix arm EHABI code to work. armhf had exception test failing without EHABI support.
No known upstream bug about this. Actual code change is more like workaround than
something that upstream would accept. Proper fix would be adding _Unwind_Control_Block
to clang unwind.h. _Unwind_Control_Block should also extend _Unwind_Exception to make
sure their ABI stays in sync.
No known upstream bug about this.
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxxabi-arm-ehabi-fix.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxx-test-fix-lockfree-test-for-i386
Lock is_always_lock free test fails on i386 because std::atomic is aligned
Lock is_always_lock free test fails on i386 because std::atomic is aligned
to 8 bytes while long long is aligned to 4 bytes. clang can't generate inline
code for unaligned 8 byte atomics even tough instruction set and gcc support
it.
That makes it expected thaqt ATOMIC_LLONG_LOCK_FREE and
std::atomic<long long>::is_always_lock_free don't match on i386. Correct test
for std::atomic<long long> is to check if target cpu support cmpxchg8 instruction.
To set instruction support one can check __GCC_HAVE_SYNC_COMPARE_AND_SWAP_8 define.
Bug: https://llvm.org/bugs/show_bug.cgi?id=19355
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxx-test-fix-lockfree-test-for-i386.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
libcxxabi-test-don-t-fail-extended-long-double
Powerpc has extended double that doesn't match x86 coding. Power format would
need special tests to verify correctness but for now it is enough to prevent
incorrect test from running.
Gbp-Pq: Topic libcxx
Gbp-Pq: Name libcxxabi-test-don-t-fail-extended-long-double.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
openmp-check-execstack
===================================================================
Gbp-Pq: Topic openmp
Gbp-Pq: Name openmp-check-execstack.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
disable-error-xray
===================================================================
Gbp-Pq: Name disable-error-xray.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
lldb-missing-install
===================================================================
Gbp-Pq: Topic lldb
Gbp-Pq: Name lldb-missing-install.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
lldb-addversion-suffix-to-llvm-server-exec
lldb-server exec users always /usr/bin/lldb-server. Server is required
for any debugging with lldb which makes it unusable unless default version
package has been installed. Small changes to code and debian/rules allows
a workaround for lldb-server start up.
To use this one needs to add cmake definition during configure. eg
-DDEBIAN_VERSION_SUFFIX=-$(LLVM_VERSION)
Better implementation would be to use /usr/share/llvm-$(VERSION)/bin but
that change seems to require a big change to the path handling code
which could then break something else.
This probably should have upstream bug but I couldn't find any existing report.
Gbp-Pq: Topic lldb
Gbp-Pq: Name lldb-addversion-suffix-to-llvm-server-exec.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
fix-scan-view-path
===================================================================
Gbp-Pq: Name fix-scan-view-path.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
scan-view-fix-path
===================================================================
Gbp-Pq: Name scan-view-fix-path.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
scan-build-clang-path
Gbp-Pq: Name scan-build-clang-path.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
test-keep-alive
===================================================================
Gbp-Pq: Name test-keep-alive.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
disable-path-test-failing
===================================================================
Gbp-Pq: Name disable-path-test-failing.diff
Sylvestre [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
Silent a test failing on yakkety amd64
Last-Update: 2016-08-26
/tmp/buildd/llvm-toolchain-snapshot-4.0~svn279801/llvm/test/tools/llvm-symbolizer/print_context.c:16:11: error: expected string not found in input
// CHECK: inc
^
<stdin>:1:1: note: scanning from here
_fini
^
<stdin>:1:3: note: possible intended match here
_fini
^
Gbp-Pq: Name disable-llvm-symbolizer-test.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
remove-test-freezing
===================================================================
Gbp-Pq: Name remove-test-freezing.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
silent-llvm-isel-fuzzer
===================================================================
Gbp-Pq: Name silent-llvm-isel-fuzzer.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
silent-test-macho
===================================================================
Gbp-Pq: Name silent-test-macho.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
silent-test-failing-codeverage
===================================================================
Gbp-Pq: Name silent-test-failing-codeverage.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
silent-gold-utils
Gbp-Pq: Name silent-gold-utils.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
silent-MCJIIT-tests
Gbp-Pq: Name silent-MCJIIT-tests.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
silent-more-tests
# Comment the tests for the code coverage (fails otherwise)
Gbp-Pq: Name silent-more-tests.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
fails on debian unstable amd64
Command Output (stderr):
--
/build/llvm-toolchain-snapshot-4.0~svn279916/llvm/test/tools/gold/X86/start-lib-common.ll:22:10: error: expected string not found in input
; CHECK: @x = common global i32 0, align 8
^
<stdin>:1:1: note: scanning from here
; ModuleID = '/build/llvm-toolchain-snapshot-4.0~svn279916/build-llvm/llvm/test/tools/gold/X86/Output/start-lib-common.ll.tmp3.o'
^
<stdin>:4:1: note: possible intended match here
@x = common global i32 0, align 4
^
Gbp-Pq: Name silent-gold-test.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
openmp-soname
===================================================================
Gbp-Pq: Name openmp-soname.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
lldb-soname
Gbp-Pq: Topic lldb
Gbp-Pq: Name lldb-soname.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
soname
Gbp-Pq: Name 0044-soname.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
do-not-fail-on-unexpected-pass
===================================================================
Gbp-Pq: Name do-not-fail-on-unexpected-pass.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
debug-jit-path
===================================================================
Gbp-Pq: Name debug-jit-path.diff
Peter Wu [Fri, 4 May 2018 13:55:26 +0000 (15:55 +0200)]
[PATCH] [clang] cmake: resolve symlinks in ClangConfig.cmake
Ensure that symlinks such as /usr/lib/cmake/clang-X.Y (pointing to
/usr/lib/llvm-X.Y/lib/cmake/llvm) are resolved. This ensures that
CLANG_INSTALL_PREFIX ends up to be /usr/lib/llvm-X.Y instead of /usr.
Partially addresses PR37128
Gbp-Pq: Name 0001-tools-clang-cmake-resolve-symlinks-in-ClangConfig.cmake.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
clang-tidy-run-bin
===================================================================
Gbp-Pq: Name clang-tidy-run-bin.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
symbolizer-path
===================================================================
Gbp-Pq: Name symbolizer-path.diff
Nicholas D Steeves [Sun, 11 Feb 2018 02:00:55 +0000 (21:00 -0500)]
Set html_static_path = ['_static'] everywhere.
Gbp-Pq: Name 0048-Set-html_static_path-_static-everywhere.patch
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
fix-clang-path-and-build
===================================================================
Gbp-Pq: Name fix-clang-path-and-build.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
python-clangpath
Gbp-Pq: Name python-clangpath.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
unwind-chain-inclusion
# Without this patch, the first local include of unwind.h might, with the
# __has_include_next, try to include the one from the system.
# It might be /usr/include/clang/3.4/include/unwind.h
# Because of the #ifndef __CLANG_UNWIND_H, it might never include any declaration
# from the system.
Gbp-Pq: Name unwind-chain-inclusion.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
declare_clear_cache
Gbp-Pq: Name declare_clear_cache.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
strlcpy_strlcat_warning_removed
Gbp-Pq: Name 23-strlcpy_strlcat_warning_removed.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
clang-analyzer-force-version
# Force the version of clang in the analyzer
# This was causing the static analyzer to fail silently if the clang & clang++ are
# not installed
Gbp-Pq: Name clang-analyzer-force-version.diff
LLVM Packaging Team [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
clang-format-version
Gbp-Pq: Name clang-format-version.diff
Sylvestre Ledru [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
llvm-toolchain-19 (1:19.1.7-1) unstable; urgency=medium
[ Matthias Klose ]
* Update libclang1 symbols file.
[ Sylvestre Ledru ]
* New upstream release
* Rewrite qualify-clang.sh with bats
Might fail on some archs
* Tests: integration-test-suite-test
Remove explicit dep libstdc++-14
[dgit import unpatched llvm-toolchain-19 1:19.1.7-1]
Sylvestre Ledru [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
Import llvm-toolchain-19_19.1.7.orig.tar.xz
[dgit import orig llvm-toolchain-19_19.1.7.orig.tar.xz]
Sylvestre Ledru [Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)]
Import llvm-toolchain-19_19.1.7-1.debian.tar.xz
[dgit import tarball llvm-toolchain-19 1:19.1.7-1 llvm-toolchain-19_19.1.7-1.debian.tar.xz]