| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
So that users of the memory map API can know if a view has activated the memory map and adjust behavior accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Turns out, you can just pass this thing an architecture that is
*completely* different from the one in the platform you are also passing
in and it'll just happily do the wrong thing. While that's pretty wild,
I'm in favor of not having to make this particular mistake again the
next time I copy/paste some code, so we're now deprecating it.
|
|
|
|
|
|
|
|
This allows us to construct a symbol without constructing a namespace, while also giving us the ability to specify raw, long, short names
|
|
|
|
|
|
|
|
This allows a consumer to bypass the alloc + free of the API NameSpace, removing the need for the consumer to manually construct a symbol for said behavior.
|
|
The usage of `DisassemblyTextLine` in the FFI was unsound, we would forget to initialize some fields causing a myriad of issues where round-tripping through the FFI was losing information.
|
|
|
|
|
|
Fixes #6397
|
|
|
|
|
|
`mul` is aligned with at least what x86 returns for tokens.
Signed-off-by: Dusk Banks <me@bb010g.com>
|
|
|
|
|
|
|
|
|
|
This reverts commit 1699c71999d29d32aba5c9f8fea193a661a4b02b.
|
|
|
