const register volatile unsigned int b asm("eax") = *(int*)(&a - sizeof(a));
Const register volatile unsigned int b asm("eax") = *(int*)(&a - sizeof(a));
Zachary Reed
Camden Carter
ur gay fuk u faget
Carson Richardson
Great thread.
Matthew Harris
auto b = *(&a - 4);
fixed
Kevin Jenkins
>let me just add keywords that don't do anything for no reason other than to make this line longer
>look how long this line is!
cool
Luis Davis
>that don't do anything
retard
John Bennett
All modern compilers ignore the register keyword
Carson Jones
No they don't
Angel Brooks
There are some poorly maintained old compilers that will allow you to use it exclusively to either hamper performance or do nothing, but the commonly used compilers will ignore it in C, and all compilers will ignore it in C++ (by spec)
Colton Lopez
On my version of GCC, the register keyword is used when no optimizations are being used. I'm guessing later versions do similar instead of outright ignoring it
Oliver Perry
>GCC
I explicitly excluded "poorly maintained old compilers"
Jaxson Reed
lol
Cameron Williams
>the register keyword is used when no optimizations are being used
The only thing gcc uses it for is the 'asm("eax")' bit. If you don't include that then the register hint doesn't do anything.
Jacob Nelson
Okay, am I the only retard in this thread? What does this code do?
> *(int*)(&a - sizeof(a))
Value of the integer that is defined just after a? (or just before a?)
> const register volatile unsigned int b asm("eax")
Yo wtf
Lincoln Cook
> const register volatile unsigned int b asm("eax")
doesn't do anything important, basically just
unsigned int b
>Value of the integer that is defined just after a? (or just before a?)
close
Aiden Carter
I tried to compile this and gcc produced this video file...
Dominic Barnes
pointer to an integer pointer, address of a minus the bytes of a
Nicholas Lee
>register volatile
The "register" keyword is a suggestion to the compiler that a variable should be stored in a CPU register, rather than in memory. The entire point of volatile variables, however, is that we assume that this is a location in memory, which may provide inconsistent values between reads (i.e. an I/O register). These two properties contradict each other.
Mason White
it's incredible that he never realised the 4 freedoms are to
Execute (the code, HoW You LIkE)
Read (the source)
Write (the source, aka a copy)
Write (modified source, which only courts see as a different permission to writing the source due to homosexual patent law)
Luis Russell
aren't you assuming a's type?
Jaxson Diaz
you can do that in C but not in nufag langauges like Rust