How do i convert a void* to a unsigned long*?

[DixiumOS]

I am trying to load ISR's. However, i have 32 isr(num) void type functions. Since my function only accepts uint32_t's or unsigned long's, i would like to convert my functions to a uint32_t*, unsigned long* or similar.

(the function is just a void, i point to it in the function).
If i try to do (uintptr_t)isr[num]();, it gives "invalid use of void expression".

If i try (uintptr_t*), same thing.

How would i convert this?

[hgoel]

By reading up on function pointers and seeing what extra stuff you you have there.

[dozniak]

How would i convert this?

Keep in mind, this forum is not for teaching beginner-level programming topics.

[dchapiesky]

assembly language would be a superior way of accomplishing this task

[DixiumOS]

Looks like i get invalid void expression every time i try to do

Code: Select all

&(uint32_t)isr[num]()

or

Code: Select all

&(unsigned long)isr[num]()

or any other. I'm gonna try to switch my function type to an unsigned int and convert it to a unsigned long (same size) and see if that works.

[DixiumOS]

Finally fixed it.

I had to make my function type an int then in the function do

Code: Select all

(unsigned)isr[num]()

.

[Octocontrabass]

Finally fixed it.

No you didn't.

Just like with your terminal_writechar and terminal_writestring (which are both still broken, by the way), your code is obviously wrong.

As suggested in an earlier post, you need to research function pointers.

[DixiumOS]

Finally fixed it.

No you didn't.

Just like with your terminal_writechar and terminal_writestring (which are both still broken, by the way), your code is obviously wrong.

As suggested in an earlier post, you need to research function pointers.

I didn't even need the pointer, anyway. The tutorial also puts (unsigned), but had the wrong types on the other file, i had to tweak things, i got on a completely different road (when i asked this question), and then went to the correct thing.

Now my only error/warning is a one that i can't seem to understand.

"Just like with your terminal_writechar and terminal_writestring (which are both still broken, by the way)"
I think you looked at the first few posts, and ignored the entire rest

[Octocontrabass]

I didn't even need the pointer, anyway.

So if you don't need the pointer, then what exactly are you putting in your IDT? (And where is your assembly wrapper for your ISRs? You can't do IRET in inline assembly.)

Now my only error/warning is a one that i can't seem to understand.

This is why we keep telling you to learn C before you start writing an OS.

"Just like with your terminal_writechar and terminal_writestring (which are both still broken, by the way)"
I think you looked at the first few posts, and ignored the entire rest

No, I'm looking at your repo. Broken code everywhere.

[DixiumOS]

"Just like with your terminal_writechar and terminal_writestring (which are both still broken, by the way)"
I think you looked at the first few posts, and ignored the entire rest

No, I'm looking at your repo. Broken code everywhere.

I still haven't updated that.

[Octocontrabass]

Now you've updated it, but your code is still broken. You still aren't using function pointers correctly (and even if you were, you still can't use IRET in inline assembly).

[hgoel]

Now you've updated it, but your code is still broken. You still aren't using function pointers correctly (and even if you were, you still can't use IRET in inline assembly).

Technically you can, it just needs a lot more care. Agreed on the rest though.