The Place to Start for Operating System Developers
https://f.osdev.org/
I saw this somewhere in Linux kernel some time ago and I can't remember exactly where it is. I need some time to search:-)NickJohnson wrote:Perhaps this is an attempt to force p to not be optimized out of the stack frame or to force a write to memory. It's particularly odd that &p is being cast to int**, considering that it already is that type. I'm assuming you found this in Linux: where did you find it? It may be part of a more elaborate hack.
A possibility never to be ruled out easily.Jezze wrote:Perhaps just a very bad programmer? =)
Maybe...berkus wrote:You might be reading it wrong.
For me, declarations like:Jezze wrote:Perhaps just a very bad programmer? =)
Code: Select all
int *p = NULL, n = xxx;yes, n is a int, so I added & and the focus is actually on the second statement.AJ wrote:Hi,
For me, declarations like:Jezze wrote:Perhaps just a very bad programmer? =)always ring alarm bells anyway, even if, as in your example above, it was intended that n is not a pointer.Code: Select all
int *p = NULL, n = xxx;
Cheers,
Adam
I'm not saying your example got it wrong. It may just be a matter of preference, but I was just saying that declaring a type and a pointer to that type in the same statement is not always the clearest way of doing it.AJ wrote:even if, as in your example above, it was intended that n is not a pointer.