Rework MTX#136
Conversation
597a26b to
4bac830
Compare
Report for RSPE01_01 (167f5f6 - a39cd06)📈 Matched code: 33.21% (+0.09%, +3176 bytes) ✅ 21 new matches
🥀 1 broken match
📈 1 improvement in an unmatched item
|
Co-Authored-By: Kiwi <49212064+kiwi515@users.noreply.github.com>
|
I moved away from turning off clang-format in favor of something more reinforced. I couldn't fix the ASM macro or get good bracket behavior for the normal keyword, so unfortunately there's no validation there. There are three exceptions I had to make:
|
| * | ||
| ******************************************************************************/ | ||
|
|
||
| #define DEG2RAD 0.017453292f |
There was a problem hiding this comment.
if we #include <math.h> and define this as (M_PI / 180.0f) does this still match?
| void C_MTXLightOrtho(MtxPtr m, f32 t, f32 b, f32 l, f32 r, f32 scaleS, | ||
| f32 scaleT, f32 transS, f32 transT); | ||
|
|
||
| #define MTXIdentity PSMTXIdentity |
There was a problem hiding this comment.
do we know enough to set all of these based on the build target (release vs. debug)?
| ps_cmpo0 cr0, f7, f6; | ||
| bne nonsingular; | ||
|
|
||
| li r3, 0x0; |
There was a problem hiding this comment.
can we do FALSE/TRUE or can assembly only see macros?
|
|
||
| switch (axis) { | ||
| case 'x': | ||
| case 'X': |
There was a problem hiding this comment.
for consistency, we use curly braces to scope switch cases since it is needed in a few cases:
like this:
case 'X': {
...
}
case ... {|
|
||
| axis |= 0x20; | ||
| switch (axis) { | ||
| case 'x': |
There was a problem hiding this comment.
same braces idea here pls :>
No description provided.