- Apr 04, 2019
-
- Apr 01, 2019
-
-
Lioncash authored
Since C++17, the introduction of deduction guides for locking facilities means that we no longer need to hardcode the mutex type into the locks themselves, making it easier to switch mutex types, should it ever be necessary in the future.
-
- Mar 29, 2019
-
-
Lioncash authored
Many of these functions are carried over from Dolphin (where they aren't used anymore). Given these have no use (and we really shouldn't be screwing around with OS-specific thread scheduler handling from the emulator, these can be removed. The function for setting the thread name is left, however, since it can have debugging utility usages.
-
unknown authored
-
unknown authored
gl_shader_disk_cache: Use better compression for transferable and precompiled shader disk chache files
-
unknown authored
data_compression: Move LZ4 compression from video_core/gl_shader_disk_cache to common/data_compression
-
- Mar 27, 2019
-
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
- Mar 21, 2019
-
-
Lioncash authored
Introduced as a result of #2090, we already define the copy constructor further down below, so this isn't needed.
-
Lioncash authored
-
Lioncash authored
-
bunnei authored
-
bunnei authored
-
Lioncash authored
When #2247 was created, thread_queue_list.h was the only user of boost-related code, however #2252 moved the page table struct into common, which makes use of Boost.ICL, so we need to add the dependency to the common library's link interface again.
-
- Mar 17, 2019
-
-
bunnei authored
-
- Mar 16, 2019
-
-
Lioncash authored
We really don't need to pull in several headers of boost related machinery just to perform the erase-remove idiom (particularly with C++20 around the corner, which adds universal container std::erase and std::erase_if, which we can just use instead). With this, we don't need to link in anything boost-related into common.
-
- Mar 07, 2019
-
-
Lioncash authored
This makes the class much more flexible and doesn't make performing copies with classes that contain a bitfield member a pain. Given BitField instances are only intended to be used within unions, the fact the full storage value would be copied isn't a big concern (only sizeof(union_type) would be copied anyways). While we're at it, provide defaulted move constructors for consistency.
-
- Mar 02, 2019
-
-
Lioncash authored
Moves local global state into the Impl class itself and initializes it at the creation of the instance instead of in the function. This makes it nicer for weakly-ordered architectures, given the CreateEntry() class won't need to have atomic loads executed for each individual call to the CreateEntry class.
-
Lioncash authored
This function is only ever used within this source file and makes it easier to remove static state in the following change.
-
- Feb 27, 2019
-
-
Lioncash authored
These types are within the common library, so they should be within the Common namespace.
-
Lioncash authored
These types are within the common library, so they should be using the Common namespace.
-
Lioncash authored
Quaternion is within the common library, so it should be using the Common namespace.
-
- Feb 26, 2019
-
-
ReinUsesLisp authored
-
- Feb 24, 2019
-
-
tgsm authored
Citra can't be compiled using GCC <7 because of required C++17 support, so these version checks don't need to exist anymore.
-
- Feb 16, 2019
-
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
Fernando Sahmkow authored
-
- Feb 15, 2019
- Feb 13, 2019
-
-
fearlessTobi authored
This change needs to be made to get the code compiling again. It was suggested after a conversation with Lioncash. The conversation can be seen here: https://user-images.githubusercontent.com/20753089/45064197-b6107800-b0b2-11e8-9db8-f696299fb86a.PNG
-
Lioncash authored
Makes it consistent with the regular standard containers in terms of size representation. This also gets rid of dependence on our own type aliases, removing the need for an include.
-
Lioncash authored
The necessity of this parameter is dubious at best, and in 2019 probably offers completely negligible savings as opposed to just leaving this enabled. This removes it and simplifies the overall interface.
-
- Feb 12, 2019
-
-
ReinUsesLisp authored
-
- Feb 07, 2019
-
-
ReinUsesLisp authored
-
Frederic L authored
Co-Authored-By:
ReinUsesLisp <reinuseslisp@airmail.cc>
-
ReinUsesLisp authored
-
ReinUsesLisp authored
-