0xff
or 0xFF
and then make it a compiler error if its not correct.qword
should be 8 byte right?mov qword [generic_buffer_512], 0xff_ff_ff
mov qword [generic_buffer_512], 0xff_ff_ff_ff
warning: signed dword immediate exceeds bounds [-w+number-overflow]
warning: dword data exceeds bounds [-w+number-overflow]
0xFFFFFFFF
is a negative number, mov immediate will sign extend it into the 64 bit register, but that's not what we want, we want it zero extendedMOV r/m64, imm32
that's the one that treats it as signed mov
anything about imm64 :\mov
anything about imm64 :\ 0xFFFFFFFF
0xDEADBEEFDEADBEEF
it'll mov it in two pieces0xffffffff
and allowing sign extension to take care of the rest of the fs0xde_ad_be_ef_de_ad_be_ef
foo.asm:8: warning: signed dword immediate exceeds bounds [-w+number-overflow]
foo.asm:8: warning: dword data exceeds bounds [-w+number-overflow]
0000000000000000 <_start>:
0: 48 c7 04 25 00 00 00 movq $0xffffffffdeadbeef,0x0
7: 00 ef be ad de
0xFFFFFFFF
0xffffffffffffffff
and two movs otherwisemovabs
first and then moves from a registermovabs
first and then moves from a register dbg_print_reg
is destroys it<span style="color: #
, ">
, </span>
, <
and >
as tokens. no xml parsing required, only string searching<#aabbcc>some text</#aabbcc>
?<#aabbcc>
and </>
<span style="color: #
, ">
, </span>
, <
and >
as tokens. no xml parsing required, only string searching <#aabbcc>
and </>
</c>
I was talking about getting banned for a non-existent rule. Anyone can make up a rule and tell me I broke it. It's just like getting cancelled but in teeworlds
- i'd say my context is fitting#include <stdio.h>
int main() {
const char *owo = "That's my string, hell yeah";
printf("%.*s", 9, owo);
}
will print
That's my
(edited)#include <stdio.h>
int main() {
const char *owo = "That's my string, hell yeah";
printf("%.*s", 9, owo);
}
will print
That's my
(edited)#include <stdio.h>
int main() {
const char *owo = "That's my string, hell yeah";
printf("%.*s", 9, owo);
}
will print
That's my
(edited)uint8_t foo[] = {
[10] = 12,
[5] = 5,
};
struct
as a unary operator Foo {
a: 0x45,
}
(edited)uint8_t foo[] = {
[10] = 12,
[5] = 5,
};
Foo {
a: 0x45,
}
(edited){
xdstruct_field_expr : label colon value;
struct_field_exprs: struct_field_expr
| struct_field_exprs comma struct_field_expr
;
struct_expr : brace_left struct_field_exprs brace_right
DDNet
and DDRace
IIRCDDNet
and DDRace
IIRC X
but cs
it seems to fall both under abbreviation and Acronym? god i should go back to schoolfor the next generation
fault Err
{
OOPS,
LOTS_OF_OOPS
}
gigachad error handling