Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2024-08-02 | libctf: fix ref leak of names of newly-inserted non-root-visible typesbinutils-2_37-branch | Nick Alcock | 1 | -4/+4 | |
A bug in ctf_dtd_delete led to refs in the string table to the names of non-root-visible types not being removed when the DTD was. This seems harmless, but actually it would lead to a write down a pointer into freed memory if such a type was ctf_rollback()ed over and then the dict was serialized (updating all the refs as the strtab was serialized in turn). Bug introduced in commit fe4c2d55634c700ba527ac4183e05c66e9f93c62 ("libctf: create: non-root-visible types should not appear in name tables") which is included in binutils 2.35. libctf/ * ctf-create.c (ctf_dtd_delete): Remove refs for all types with names, not just root-visible ones. | |||||
2022-04-28 | s390: Add DT_JMPREL pointing to .rela.[i]plt with static-pie | Stefan Liebler | 1 | -1/+14 | |
In static-pie case, there are IRELATIVE-relocs in .rela.iplt (htab->irelplt), which will later be grouped to .rela.plt. On s390, the IRELATIVE relocations are always located in .rela.iplt - even for non-static case. Ensure that DT_JMPREL, DT_PLTRELA, DT_PLTRELASZ is added to the dynamic section even if htab->srelplt->size == 0. See _bfd_elf_add_dynamic_tags in bfd/elflink.c. bfd/ elf64-s390.c (elf_s390_size_dynamic_sections): Enforce DT_JMPREL via htab->elf.dt_jmprel_required. (cherry picked from commit d942d8db12adf4c9e5c7d9ed6496a779ece7149e) | |||||
2022-04-28 | s390: Avoid dynamic TLS relocs in PIE | Stefan Liebler | 1 | -13/+13 | |
No dynamic relocs are needed for TLS defined in an executable, the TP relative offset is known at link time. Fixes FAIL: Build pr22263-1 bfd/ PR ld/22263 * elf64-s390.c (elf_s390_tls_transition): Use bfd_link_dll instead of bfd_link_pic for TLS. (elf_s390_check_relocs): Likewise. (allocate_dynrelocs): Likewise. (elf_s390_relocate_section): Likewise. (cherry picked from commit 26b1426577b5dcb32d149c64cca3e603b81948a9) | |||||
2022-04-07 | IBM zSystems: Add support for z16 as CPU name. | Andreas Krebbel | 4 | -6/+7 | |
So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) | |||||
2022-03-14 | PR28959, obdump doesn't disassemble mftb instruction | Alan Modra | 1 | -2/+3 | |
Without a -M cpu option given, powerpc objdump defaults currently to -Mpower10 but -Many is also given. Commit 1ff6a3b8e562 regressed -Many disassembly of instructions that are encoded differently depending on cpu, such as mftb which has pre- and post-power4 encodings. PR 28959 * ppc-dis.c (lookup_powerpc): Revert 2021-05-28 change. Instead only look at deprecated PPC_OPCODE_RAW bit when -Many. (cherry picked from commit b508e46bf9c5b2cef5821b399dfc3b8009a81836) | |||||
2022-02-07 | i386: Allow GOT32 relocations against ABS symbols | H.J. Lu | 4 | -4/+23 | |
GOT32 relocations are allowed since absolute value + addend is stored in the GOT slot. Tested on glibc 2.35 build with GCC 11.2 and -Os. bfd/ PR ld/28870 * elfxx-x86.c (_bfd_elf_x86_valid_reloc_p): Also allow GOT32 relocations. ld/ PR ld/28870 * testsuite/ld-i386/i386.exp: Run pr28870. * testsuite/ld-i386/pr28870.d: New file. * testsuite/ld-i386/pr28870.s: Likewise. (cherry picked from commit 30a954525f4e53a9cd50a1a8a6f201c7cf6595c7) | |||||
2022-01-22 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-21 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-20 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-19 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-18 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-17 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-16 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-15 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-14 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-13 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-12 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-11 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-10 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-09 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-08 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-07 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-06 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-05 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-04 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-03 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-02 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2022-01-01 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-31 | -Waddress warning in ldelf.c | Alan Modra | 1 | -1/+0 | |
ldelf.c: In function 'ldelf_after_open': ldelf.c:1049:43: warning: the comparison will always evaluate as 'true' for the address of 'elf_header' will never be NULL [-Waddress] 1049 | && elf_tdata (abfd)->elf_header != NULL | ^~ In file included from ldelf.c:37: ../bfd/elf-bfd.h:1957:21: note: 'elf_header' declared here 1957 | Elf_Internal_Ehdr elf_header[1]; /* Actual data, but ref like ptr */ PR ld/28734 * ldelf.c (ldelf_after_open): Remove useless elf_header test. (cherry picked from commit ced10cb78d01652f9e1bb1d1e465327dfe1debaa) | |||||
2021-12-31 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-30 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-29 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-28 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-27 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-26 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-25 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-24 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-23 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-22 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-21 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-20 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-19 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-18 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-17 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-16 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-15 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-14 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-13 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-12 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2021-12-11 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |