Commit Graph

119557 Commits

Author SHA1 Message Date
GDB Administrator
6d4aa19e6d Automatic date update in version.in 2025-01-19 00:01:58 +00:00
GDB Administrator
580f378987 Automatic date update in version.in 2025-01-18 00:00:52 +00:00
Andrew Carlotti
61f8adadd6 aarch64: Fix sve2p1 gating and add missing instructions
Many FEAT_SVE2p1 instructions need to be enabled by either of two
different features (one for streaming mode, and one for non-streaming
mode).  This patch adds correct gating conditions for these
instructions.

There were also a few sve2p1 instructions missing altogether, so add
those as well.

The testsuite is modified to check for all alternative enablement
conditions.  In many cases this is done by adding an alternative
assembler commands to existing test files.  For some SME/SME2 tests,
only some of the instructions are enabled by +sve2p1, so these are
copied into a separate test.  For original SVE2p1 tests, the non-SME2p1
instructions have been moved to a separate test file.

There are also new tests for the newly added instructions.  These
include a couple of fixme comments relating to bad error reporting,
which should be investigated later.
2025-01-17 16:42:54 +00:00
GDB Administrator
a5f8f36803 Automatic date update in version.in 2025-01-17 00:03:09 +00:00
GDB Administrator
f8b2cac2c9 Automatic date update in version.in 2025-01-16 00:03:33 +00:00
GDB Administrator
db46436a9d Automatic date update in version.in 2025-01-15 00:02:04 +00:00
GDB Administrator
a34cfe6ead Automatic date update in version.in 2025-01-14 00:02:57 +00:00
GDB Administrator
c378d57265 Automatic date update in version.in 2025-01-13 00:01:56 +00:00
GDB Administrator
dd0ec14a09 Automatic date update in version.in 2025-01-12 00:01:53 +00:00
GDB Administrator
e0648d13bf Automatic date update in version.in 2025-01-11 00:00:55 +00:00
Andrew Carlotti
09bfea4a2f aarch64: Fix incorrect gating of sme-lutv2 instructions
Only the strided form of the luti4 intrinsic requires FEAT_SME2p1.
2025-01-10 16:33:51 +00:00
GDB Administrator
5f9760576b Automatic date update in version.in 2025-01-10 00:01:09 +00:00
GDB Administrator
ccc4a18389 Automatic date update in version.in 2025-01-09 00:02:45 +00:00
GDB Administrator
b5f78ac514 Automatic date update in version.in 2025-01-08 00:01:48 +00:00
GDB Administrator
a7382227ff Automatic date update in version.in 2025-01-07 00:01:45 +00:00
GDB Administrator
52a4aa63dc Automatic date update in version.in 2025-01-06 00:02:54 +00:00
GDB Administrator
db05ea275f Automatic date update in version.in 2025-01-05 00:01:39 +00:00
Alan Modra
01da089627 _bfd_write_ar_hdr
This has been broken since commit 8f95b6e449 in 2010, and apparently
nobody has noticed.  How we write archive headers depends on the
archive, not the contents.

	* libbfd-in.h (_bfd_write_ar_hdr): Correct.
	* libbfd.h: Regenerate.

(cherry picked from commit c232d080c4)
2025-01-04 19:26:31 +10:30
Alan Modra
412919cb96 PR32266, segv when linking libclang_rt.asan-powerpc64.so
Change the mmap support added with commit 9ba56acee5 to always mmap
memory with PROT_READ | PROT_WRITE.  Prior to that commit most file
contents were read into a buffer allocated with bfd_alloc or
bfd_malloc and thus the memory was read/write.  Even after that commit
any section contents with relocations must be read/write to apply the
relocs.  Making them all read/write is not a major change, and it
should not introduce any measurable linker slowdown for contents that
are not modified.  More importantly, it removes a BFD behaviour
difference that only triggers when large files are involved.

	PR 32266
	PR 32109
	* libbfd.c (bfd_mmap_local): Remove prot param.  Always mmap
	with PROT_READ | PROT_WRITE.  Adjust all calls.
	(_bfd_mmap_temporary): Rename from _bfd_mmap_readonly_temporary.
	(_bfd_munmap_temporary): Rename from _bfd_munmap_readonly_temporary.
	_bfd_mmap_persistent): Rename from _bfd_mmap_readonly_persistent.
	(_bfd_generic_get_section_contents): Use PROT_READ | PROT_WRITE
	regardless of relocs.
	* libbfd-in.h: Update decls to suit.  Make non-USE_MMAP variants
	static inline functions.
	* elflink.c: Update all uses of _bfd_mmap functions.
	* elf.c: Likewise.
	(bfd_elf_get_str_section): Revert commit 656f8fbaae.
	* libbfd.h: Regenerate.

(cherry picked from commit 76eab8f47a)
2025-01-04 19:23:39 +10:30
GDB Administrator
9a315cb6ea Automatic date update in version.in 2025-01-04 00:01:37 +00:00
GDB Administrator
040dae45b6 Automatic date update in version.in 2025-01-03 00:02:15 +00:00
GDB Administrator
b5535e1eba Automatic date update in version.in 2025-01-02 00:02:52 +00:00
GDB Administrator
079dad9234 Automatic date update in version.in 2025-01-01 00:02:14 +00:00
GDB Administrator
aeed5c1838 Automatic date update in version.in 2024-12-31 00:02:11 +00:00
mengqinggang
bb9a0a36e7 LoongArch: Add relaxation support for call36 that jump to PLT entry
Part of commit a104f0a3e6 ("LoongArch: Add more relaxation support for
call36") in master.  This part is needed for 2.43 branch to fix a link
failure of QtWebEngine-6.8.1, which can be demonstrated with a reduced
test case (with -shared):

    .text
    .zero 1 << 27   # pretending we have a lot of code in .text
    .globl f        # preemptible, thus must be called via PLT
    f:
      move $a0, $r0
      ret
    g:
      pcaddu18i $t0, %call36(f)
      jr $t0

Signed-off-by: Xi Ruoyao <xry111@xry111.site>
2024-12-30 09:40:14 +08:00
GDB Administrator
e17aa8bbd8 Automatic date update in version.in 2024-12-30 00:02:15 +00:00
GDB Administrator
2c1975500d Automatic date update in version.in 2024-12-29 00:01:52 +00:00
Xi Ruoyao
a8563dba75 LoongArch: Fix broken DESC => IE transition for 2.43 branch
If code compiled with -fPIC -mtls-dialect=desc is linked into a PDE or
PIE, and the code refers to external DSO symbols, we can produce broken
link unit as check_relocs expects DESC => IE transition to happen and
emits a TLS IE entry in the GOT, but a too early "continue" in
relax_section actually jumps over the DESC => IE transition so the code
sequence is unchanged and still expecting a TLS descriptor (instead of
an IE entry) in the GOT.

The bug is already fixed in master branch by commit 5c3d09c185
("LoongArch: Optimize the relaxation process") so this fix is only
needed for the 2.43 branch.

Reported-by: Icenowy Zheng <uwu@icenowy.me>
Closes: https://gcc.gnu.org/PR118114
Tested-by: Icenowy Zheng <uwu@icenowy.me>
Signed-off-by: Xi Ruoyao <xry111@xry111.site>
2024-12-28 16:28:27 +08:00
GDB Administrator
e2d776f7b9 Automatic date update in version.in 2024-12-28 00:02:36 +00:00
GDB Administrator
0cdfcb9b8c Automatic date update in version.in 2024-12-27 00:02:07 +00:00
GDB Administrator
923497873f Automatic date update in version.in 2024-12-26 00:01:55 +00:00
GDB Administrator
551c1430e5 Automatic date update in version.in 2024-12-25 00:00:52 +00:00
GDB Administrator
b194ae062e Automatic date update in version.in 2024-12-24 00:00:58 +00:00
GDB Administrator
33990e5ced Automatic date update in version.in 2024-12-23 00:01:14 +00:00
GDB Administrator
fdef3910ed Automatic date update in version.in 2024-12-22 00:00:48 +00:00
GDB Administrator
44da930420 Automatic date update in version.in 2024-12-21 00:01:50 +00:00
GDB Administrator
8f2c68b59c Automatic date update in version.in 2024-12-20 00:01:58 +00:00
Jan Beulich
808a2dae2f x86-64: correct CODE_5 relocs
Two of them had their numbers swapped; luckily they aren't really in use
just yet. Correct indentation as well while at it.
2024-12-19 10:41:20 +01:00
GDB Administrator
1ec1931df8 Automatic date update in version.in 2024-12-19 00:02:45 +00:00
GDB Administrator
5a912df92d Automatic date update in version.in 2024-12-18 00:01:11 +00:00
Nick Clifton
5f8987d399 nm: Avoid potential segmentation fault when displaying symbols without version info.
PR 32467
2024-12-17 09:18:57 +00:00
GDB Administrator
36a68f94e5 Automatic date update in version.in 2024-12-17 00:02:22 +00:00
GDB Administrator
b6da720d9f Automatic date update in version.in 2024-12-16 00:01:49 +00:00
GDB Administrator
e2622c0a84 Automatic date update in version.in 2024-12-15 00:00:57 +00:00
GDB Administrator
bcf18c37bf Automatic date update in version.in 2024-12-14 00:01:50 +00:00
GDB Administrator
834b779ad2 Automatic date update in version.in 2024-12-13 00:01:10 +00:00
GDB Administrator
469cb3e5e6 Automatic date update in version.in 2024-12-12 00:01:16 +00:00
GDB Administrator
30cc652cd5 Automatic date update in version.in 2024-12-11 00:02:20 +00:00
GDB Administrator
b1a59f5d69 Automatic date update in version.in 2024-12-10 00:00:44 +00:00
GDB Administrator
2c9f7154ba Automatic date update in version.in 2024-12-09 00:01:44 +00:00