Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-06-22 | ImageDecoder: Add a new service for out-of-process image decoding :^) | Andreas Kling | |
The new ImageDecoder service (available for members of "image" via /tmp/portal/image) allows you to decode images in a separate process. This will allow programs to confidently load untrusted images, since the bulk of the security concerns are sandboxed to a separate process. The only API right now is a synchronous IPC DecodeImage() call that takes a shbuf with encoded image data and returns a shared buffer and metadata for the decoded image. It also comes with a very simple library for interfacing with the ImageDecoder service: LibImageDecoderClient. The name is a bit of a mouthful but I guess we can rename it later if we think of something nicer to call it. There's obviously a bit of overhead to spawning a separate process for every image decode, so this is mostly only appropriate for untrusted images (e.g stuff downloaded from the web) and not necessary for trusted local images (e.g stuff in /res) | |||
2020-06-03 | LibKeyboard: Add new library for keyboard applications | Hüseyin ASLITÜRK | |
Move shared code base from keymap and KeyboardMapper to this library. | |||
2020-05-20 | Revert "LibC: Implement Itanium C++ ABI for static variable guards" | Andreas Kling | |
This reverts commit cdbbe14062ea49f9a9d9b0e5627aba9efd07659a. | |||
2020-05-20 | LibC: Implement Itanium C++ ABI for static variable guards | Andrew Kaster | |
This is __cxa_guard_acquire, __cxa_guard_release, and __cxa_guard_abort. We put these symbols in a 'fake' libstdc++ to trick gcc into thinking it has libstdc++. These symbols are necessary for C++ programs and not C programs, so, seems file. There's no way to tell gcc that, for example, the standard lib it should use is libc++ or libc. So, this is what we have for now. When threaded code enters a block that is trying to call the constructor for a block-scope static, the compiler will emit calls to these methods to handle the "call_once" nature of block-scope statics. The compiler creates a 64-bit guard variable, which it checks the first byte of to determine if the variable should be intialized or not. If the compiler-generated code reads that byte as a 0, it will call __cxa_guard_acquire to try and be the thread to call the constructor for the static variable. If the first byte is 1, it will assume that the variable's constructor was called, and go on to access it. __cxa_guard_acquire uses one of the 7 implementation defined bytes of the guard variable as an atomic 8 bit variable. To control a state machine that lets each entering thread know if they gained 'initialization rights', someone is working on the varaible, someone is working on the varaible and there's at least one thread waiting for it to be intialized, or if the variable was initialized and it's time to access it. We only store a 1 to the byte the compiler looks at in __cxa_guard_release, and use a futex to handle waiting. | |||
2020-05-17 | LibGemini: Implement basic Gemini protocol support | Conrad Pankoff | |
2020-05-14 | Build: Switch to CMake :^) | Sergey Bugaev | |
Closes https://github.com/SerenityOS/serenity/issues/2080 |