Skip to content

T
Third Party Musl

OpenHarmony / Third Party Musl
10 个月 前同步成功

通知 37
Star 125
Fork 0
T
Third Party Musl

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
  1. 05 8月, 2022 1 次提交
  3. 02 8月, 2022 1 次提交
  5. 01 8月, 2022 1 次提交
  7. 29 7月, 2022 1 次提交
  9. 25 7月, 2022 1 次提交
  11. 22 7月, 2022 1 次提交
  13. 12 7月, 2022 2 次提交
  15. 06 7月, 2022 1 次提交
  17. 04 7月, 2022 1 次提交
  19. 24 6月, 2022 1 次提交
  21. 23 6月, 2022 1 次提交
  23. 22 6月, 2022 1 次提交
  25. 10 5月, 2022 1 次提交
  27. 21 4月, 2022 2 次提交
  29. 20 4月, 2022 2 次提交
  31. 18 4月, 2022 1 次提交
  33. 29 3月, 2022 1 次提交
  35. 15 3月, 2022 1 次提交
  37. 09 3月, 2022 1 次提交
  39. 07 3月, 2022 1 次提交
  41. 16 2月, 2022 1 次提交
  43. 11 1月, 2022 1 次提交
  45. 11 6月, 2021 1 次提交
  47. 31 8月, 2020 1 次提交
  49. 20 8月, 2020 1 次提交
  51. 19 8月, 2020 1 次提交
  53. 17 8月, 2020 1 次提交
  55. 16 1月, 2020 1 次提交
    • R
      fix incorrect __hwcap seen in dynamic-linked __set_thread_area · 0ff18be2
      由 Rich Felker 提交于 
      the bug fixed in commit b82cd6c7 was
mostly masked on arm because __hwcap was zero at the point of the call
from the dynamic linker to __set_thread_area, causing the access to
libc.auxv to be skipped and kuser_helper versions of TLS access and
atomics to be used instead of the armv6 or v7 versions. however, on
kernels with kuser_helper removed for hardening it would crash.

since __set_thread_area potentially uses __hwcap, it must be
initialized before the function is called. move the AT_HWCAP lookup
from stage 3 to stage 2b.
      0ff18be2
  57. 01 1月, 2020 3 次提交
    • R
      fix fdpic regression in dynamic linker with overly smart compilers · d6bbea2a
      由 Rich Felker 提交于 
      at least gcc 9 broke execution of DT_INIT/DT_FINI for fdpic archs
(presently only sh) by recognizing that the stores to the
compound-literal function descriptor constructed to call them were
dead stores. there's no way to make a "may_alias function", so instead
launder the descriptor through an asm-statement barrier. in practice
just making the compound literal volatile seemed to have worked too,
but this should be less of a hack and more accurately convey the
semantics of what transformations are not valid.
      d6bbea2a
    • R
      fix crashing ldso on archs where __set_thread_area examines auxv · b82cd6c7
      由 Rich Felker 提交于 
      commit 1c84c999 moved the call to
__init_tp above the initialization of libc.auxv, inadvertently
breaking archs where __set_thread_area examines auxv for the sake of
determining the TLS/atomic model needed at runtime. this broke armv6
and sh2.
      b82cd6c7
    • R
      move stage3_func typedef out of shared internal dynlink.h header · b529ec9b
      由 Rich Felker 提交于 
      this interface contract is entirely internal to dynlink.c.
      b529ec9b
  59. 03 11月, 2019 1 次提交
    • R
      add time64 redirect for, and redirecting implementation of, dlsym · 22daaea3
      由 Rich Felker 提交于 
      if symbols are being redirected to provide the new time64 ABI, dlsym
must perform matching redirections; otherwise, it would poke a hole in
the magic and return pointers to functions that are not safe to call
from a caller using time64 types.

rather than duplicating a table of redirections, use the time64
symbols present in libc's symbol table to derive the decision for
whether a particular symbol needs to be redirected.
      22daaea3
  61. 14 8月, 2019 1 次提交
    • R
      fix regression whereby main thread didn't get TLS relocations · 9d35fec9
      由 Rich Felker 提交于 
      commit ffab4360 broke this by moving
relocations after not only the allocation of storage for the main
thread's static TLS, but after the copying of the TLS image. thus,
relocation results were not reflected in the main thread's copy. this
could be fixed by calling __reset_tls after relocations, but instead
split the allocation and installation before/after relocations so that
there's not a redundant copy.

due to commit 71af5309, updating of
static_tls_cnt needs to be kept with allocation of static TLS, before
relocations, rather than after installation.
      9d35fec9
  63. 13 8月, 2019 2 次提交
    • S
      make relocation time symbol lookup and dlsym consistent · f2435263
      由 Szabolcs Nagy 提交于 
      Using common code path for all symbol lookups fixes three dlsym issues:

- st_shndx of STT_TLS symbols were not checked and thus an undefined
  tls symbol reference could be incorrectly treated as a definition
  (the sysv hash lookup returns undefined symbols, gnu does not, so should
  be rare in practice).

- symbol binding was not checked so a hidden symbol may be returned
  (in principle STB_LOCAL symbols may appear in the dynamic symbol table
  for hidden symbols, but linkers most likely don't produce it).

- mips specific behaviour was not applied (ARCH_SYM_REJECT_UND) so
  undefined symbols may be returned on mips.

always_inline is used to avoid relocation performance regression, the
code generation for find_sym should not be affected.
      f2435263
    • R
      ldso: correct condition for local symbol handling in do_relocs · 1f060ed2
      由 Rich Felker 提交于 
      commit 7a9669e9 added use of the
symbol reference as the definition, in place of performing a lookup,
for STT_SECTION symbol references that were first found used in FDPIC.
such references may happen in certain other cases, such as
local-dynamic TLS and with relocation types that require a symbol but
that are being used for non-symbolic purposes, like the powerpc
unaligned address relocations.

in all such cases I'm aware of, the symbol referenced is a section
symbol (STT_SECTION); however, the important semantic property is not
its being a section, but rather its binding local (STB_LOCAL). check
the latter instead of the former for greater generality and semantic
correctness.
      1f060ed2
  65. 12 8月, 2019 1 次提交
    • S
      add support for powerpc/powerpc64 unaligned relocations · 08869deb
      由 Samuel Holland 提交于 
      R_PPC_UADDR32 (R_PPC64_UADDR64) has the same meaning as R_PPC_ADDR32
(R_PPC64_ADDR64), except that its address need not be aligned. For
powerpc64, BFD ld(1) will automatically convert between ADDR<->UADDR
relocations when the address is/isn't at its native alignment. This
will happen if, for example, there is a pointer in a packed struct.

gold and lld do not currently generate R_PPC64_UADDR64, but pass
through misaligned R_PPC64_ADDR64 relocations from object files,
possibly relaxing them to misaligned R_PPC64_RELATIVE. In both cases
(relaxed or not) this violates the PSABI, which defines the relevant
field type as "a 64-bit field occupying 8 bytes, the alignment of
which is 8 bytes unless otherwise specified."

All three linkers violate the PSABI on 32-bit powerpc, where the only
difference is that the field is 32 bits wide, aligned to 4 bytes.

Currently musl fails to load executables linked by BFD ld containing
R_PPC64_UADDR64, with the error "unsupported relocation type 43".
This change provides compatibility with BFD ld on powerpc64, and any
static linker on either architecture that starts following the PSABI
more closely.
      08869deb
  67. 11 8月, 2019 1 次提交