1. 11 Jun, 2015 1 commit
  2. 11 Sep, 2014 1 commit
  3. 08 Sep, 2014 2 commits
    • Elliott Hughes's avatar
      Ensure __set_errno is still visible on LP32. · 011e111d
      Elliott Hughes authored
      The use of the .hidden directive to avoid going via the PLT for
      __set_errno had the side-effect of actually making __set_errno
      hidden (which is odd because assembler directives don't usually
      affect symbols defined in a different file --- you can't even
      create a weak reference to a symbol that's defined in a different
      file).
      
      This change switches the system call stubs over to a new always-hidden
      __set_errno_internal and has a visible __set_errno on LP32 just for
      binary compatibility with old NDK apps.
      
      (cherry-pick of 7efad83d.)
      
      Bug: 17423135
      Change-Id: I6b6d7a05dda85f923d22e5ffd169a91e23499b7b
      011e111d
    • Elliott Hughes's avatar
      Ensure __set_errno is still visible on LP32. · 7efad83d
      Elliott Hughes authored
      The use of the .hidden directive to avoid going via the PLT for
      __set_errno had the side-effect of actually making __set_errno
      hidden (which is odd because assembler directives don't usually
      affect symbols defined in a different file --- you can't even
      create a weak reference to a symbol that's defined in a different
      file).
      
      This change switches the system call stubs over to a new always-hidden
      __set_errno_internal and has a visible __set_errno on LP32 just for
      binary compatibility with old NDK apps.
      
      Bug: 17423135
      Change-Id: I6b6d7a05dda85f923d22e5ffd169a91e23499b7b
      7efad83d
  4. 08 Aug, 2014 3 commits
  5. 07 Aug, 2014 1 commit
    • Dan Albert's avatar
      Fix incorrect relocations for x86. · 512bc523
      Dan Albert authored
      These calls were not going through the PLT like they should have been.
      
      Bug: 16853291
      Change-Id: Id70488b077256a70137c4417f21be2c2d1d4341c
      512bc523
  6. 06 Jun, 2014 1 commit
  7. 30 May, 2014 1 commit
    • Christopher Ferris's avatar
      Fix x86 cfi directives for syscalls. · 15b91e92
      Christopher Ferris authored
      The syscall generation always used 4 bytes for each push cfi directive.
      However, the first push should always use an offset of 8 bytes, each
      subsequent push after that is only 4 bytes though.
      
      Change-Id: Ibaabd107f399ef67010b9a08213783957c2f74a9
      15b91e92
  8. 07 Jan, 2014 1 commit
  9. 07 Nov, 2013 1 commit
  10. 24 Oct, 2013 1 commit
  11. 16 Oct, 2013 1 commit
  12. 01 Oct, 2013 1 commit
    • Elliott Hughes's avatar
      Regenerate the system call stubs (to get x86_64). · e4ffd9f2
      Elliott Hughes authored
      This touches the x86 stubs too because arm, x86, and x86_64 now
      all share the same header (at a source level), which causes a
      reordering of the #include lines.
      
      Change-Id: If9a1e2b2718bd41d8399fea748bce672c513ef84
      e4ffd9f2
  13. 22 Mar, 2013 1 commit
    • Elliott Hughes's avatar
      The SYS_ constants should cover all __NR_ values. · 5c2772f5
      Elliott Hughes authored
      <sys/linux-syscalls.h> only contains constants for the syscalls
      we're generating stubs for. We want all the syscalls available
      on the architecture in question.
      
      Keep using <sys/linux-syscalls.h> on ARM for now because the
      __NR_ARM_set_tls and __NR_ARM_cacheflush values aren't in <asm/unistd.h>.
      
      Change-Id: I66683950d87d9b18d6107d0acc0ed238a4496f44
      5c2772f5
  14. 13 Mar, 2013 1 commit
  15. 07 Feb, 2013 1 commit
  16. 25 Jan, 2010 1 commit
  17. 04 Mar, 2009 2 commits
  18. 21 Oct, 2008 1 commit