1. 23 Feb, 2022 1 commit
  2. 27 Nov, 2020 1 commit
  3. 23 Jun, 2019 1 commit
  4. 31 Jan, 2019 2 commits
  5. 25 Jan, 2019 1 commit
    • streams: don't write more than SSIZE_MAX · f1986a23
      Our streams implementation takes a `size_t` that indicates the length of
      the data buffer to be written, and returns an `ssize_t` that indicates
      the length that _was_ written.  Clearly no such implementation can write
      more than `SSIZE_MAX` bytes.  Ensure that each TLS stream implementation
      does not try to write more than `SSIZE_MAX` bytes (or smaller; if the
      given implementation takes a smaller size).
      Edward Thomson committed
  6. 24 Jan, 2019 1 commit
  7. 22 Jan, 2019 1 commit
  8. 06 Jan, 2019 1 commit
    • Fix a bunch of warnings · 7b453e7e
      This change fixes a bunch of warnings that were discovered by compiling
      with `clang -target=i386-pc-linux-gnu`. It turned out that the
      intrinsics were not necessarily being used in all platforms! Especially
      in GCC, since it does not support __has_builtin.
      
      Some more warnings were gleaned from the Windows build, but I stopped
      when I saw that some third-party dependencies (e.g. zlib) have warnings
      of their own, so we might never be able to enable -Werror there.
      lhchavez committed
  9. 28 Nov, 2018 2 commits
  10. 23 Oct, 2017 1 commit
  11. 04 Oct, 2017 1 commit
  12. 03 Jul, 2017 1 commit
    • Make sure to always include "common.h" first · 0c7f49dd
      Next to including several files, our "common.h" header also declares
      various macros which are then used throughout the project. As such, we
      have to make sure to always include this file first in all
      implementation files. Otherwise, we might encounter problems or even
      silent behavioural differences due to macros or defines not being
      defined as they should be. So in fact, our header and implementation
      files should make sure to always include "common.h" first.
      
      This commit does so by establishing a common include pattern. Header
      files inside of "src" will now always include "common.h" as its first
      other file, separated by a newline from all the other includes to make
      it stand out as special. There are two cases for the implementation
      files. If they do have a matching header file, they will always include
      this one first, leading to "common.h" being transitively included as
      first file. If they do not have a matching header file, they instead
      include "common.h" as first file themselves.
      
      This fixes the outlined problems and will become our standard practice
      for header and source files inside of the "src/" from now on.
      Patrick Steinhardt committed
  13. 26 Apr, 2017 1 commit
    • socket_stream: continue to next addrinfo on socket creation failure · 954e06a8
      When connecting to a remote via socket stream, we first use getaddrinfo
      to obtain the possible connection methods followed by creating and
      connecting the socket. But when creating the socket, we error out as
      soon as we get an invalid socket instead of trying out other address
      hints returned by addrinfo.
      
      Fix this by continuing on invalid socket instead of returning an error.
      This fixes connection establishment with musl libc.
      Patrick Steinhardt committed
  14. 29 Dec, 2016 1 commit
  15. 10 Dec, 2014 4 commits