| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Signed-off-by: lizzie <lizzie@eden-emu.dev>
- [x] I have read and followed the [Contribution Guidelines](https://git.eden-emu.dev/eden-emu/eden/src/branch/master/CONTRIBUTING.md#code-contributions).
- [x] I have read and followed the [AI Policy](https://git.eden-emu.dev/eden-emu/eden/src/branch/master/docs/policies/AI.md)
- [x] I have read and followed the [Coding Guidelines](https://git.eden-emu.dev/eden-emu/eden/src/branch/master/docs/policies/Coding.md) to the best of my ability.
-------------------
We don't use half of this file for anything -- it's dead code
also the NEON intrinsic replacements suck -- we are not beating GLM (plus we use registers for decomposition instead of using vec regs like everyone else does, so the "optimizations" dont matter)
Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/4333
Reviewed-by: CamilleLaVey <camillelavey99@gmail.com>
Reviewed-by: Maufeat <sahyno1996@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
PabloMK7: Changes the Vec4 dot operation to use NEON intrinsics on ARM devices.
This function is used every time a triangle is added to the rendered, so it can be considered hot code. The other vector operations are not used as much, so there is no gain to provide NEON operations for them.
The improvements from this change are most likely minimal.
Co-authored-by: PabloMK7 <hackyglitch2@gmail.com>
Co-authored-by: Gamer64 <76565986+Gamer64ytb@users.noreply.github.com>
Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/177
Co-authored-by: Gamer64 <gamer64@eden-emu.dev>
Co-committed-by: Gamer64 <gamer64@eden-emu.dev>
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Depends on https://github.com/yuzu-emu/build-environments/pull/69
clang-15 primary run
|
| |
|
|
| |
Follow-up to 2b87305d319f0bd04da36fb96314934f37b12637
|
| | |
|
| |
|
|
|
| |
Makes the input_common code warnings consistent with the rest of the
codebase.
|
| |
|
|
|
|
| |
Now that clang-format makes [[nodiscard]] attributes format sensibly, we
can apply them to several functions within the common library to allow
the compiler to complain about any misuses of the functions.
|
| |
|
|
|
| |
These types are within the common library, so they should be using the
Common namespace.
|
| |
|
|
| |
Same behavior, less code
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Ensures that values are always in a well-defined state.
|
| |
|
|
| |
These are all unused and the Write() ones should arguably not even be in the interface. There are better ways to provide this if we ever need it (like iterators).
|
| | |
|
| |
|
|
|
| |
It is unlikely we will ever use this without first doing a Cast to a signed type.
Fixes 9 "unary minus operator applied to unsigned type, result still unsigned" warnings on MSVC2017.3
|
| | |
|
| |
|
|
| |
this was originally added to eliminate warnings on MSVC, but it doesn't work for custom types.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
They're not currently used, and it's easy to accidentally pass a single
pointer argument to them, causing an out-of-bounds read.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
silent warning C4146 on msvc
|
|
|
The file only contained vector manipulation code, and such widely-useable code doesn't belong in video_core.
|