For example if an architecture supports nibble length instructions but data is byte aligned, will:
void *PointerToAnything;
work? In other words, can the compiler handle this?
Can C cope with sub-byte instruction addressing?
139 Views Asked by ChrisKW At
1
There are 1 best solutions below
Related Questions in C
- How to call a C language function from x86 assembly code?
- What does: "char *argv[]" mean?
- User input sanitization program, which takes a specific amount of arguments and passes the execution to a bash script
- How to crop a BMP image in half using C
- How can I get the difference in minutes between two dates and hours?
- Why will this code compile although it defines two variables with the same name?
- Compiling eBPF program in Docker fails due to missing '__u64' type
- Why can't I use the file pointer after the first read attempt fails?
- #include Header files in C with definition too
- OpenCV2 on CLion
- What is causing the store latency in this program?
- How to refer to the filepath of test data in test sourcecode?
- 9 Digit Addresses in Hexadecimal System in MacOS
- My server TCP doesn't receive messages from the client in C
- Printing the characters obtained from the array s using printf?
Related Questions in COMPILER-CONSTRUCTION
- Reference: Crafting Interpreters. Print statement is not able to evaluate expression. Help me fix this (details below)
- Load function written in amd64 assembly into memory and call it
- I have implemented till Statements and State in Tree Walk Interpreter. I am pissed with an error
- Resolve shift/reduction conflict in grammar for expressions in PLY for calls to embedded functions
- Grammar for access to properties and calls to embedded functions
- LLVM code generation causes problems with pointer arithmetic
- what does react compiler mean actually?
- Errors on Recursive Descent Parsing Java
- Java CUP produces Shift-Reduce conflict when parsing a grammar for a C++ type language
- Three-Address-Code (TAC) and Conjunction/Disjunction
- How do I write an implicit cast for my strongly typed interpreter? (C++)
- Yacc parser not reducing specific production rules as intended
- Why is the function version tag consistently "Base" in HDF5 library?
- Sly parser, how are recursively defined types implemented?
- Does a non terminal token need an explicit definition?
Related Questions in MEMORY-ADDRESS
- 9 Digit Addresses in Hexadecimal System in MacOS
- Why does setting the unused bits of a virtual address cause a segfault?
- Understanding virtual to physical memory translation in Android
- Getting the address of list[0].next in Sigma16 and calling it X1
- How Python know that it has to give a new address for a variable?
- Converting virtual address to real address - in hexadecimal
- Where are real mode address contents located in protected mode?
- How do computers store variable addresses?
- Is there any problem in this MIPS code? Like address out of the bounds? What the meaning of the code?
- Why doesnt decremented pointers return the right value?
- Is it UB to reinterpret_cast a T* to a uintptr_t, reinterpret_cast that uintptr_t to a void*, then static_cast that void* back to a T*?
- Why Visual Studio memory addresses shuffle based on view?
- Understanding the interpretation of array labels
- How do I initialize an array at a specific address for CANbus RX/TX FIFO start address register (ATSAME51)?
- Logical address generation is done by the CPU or by the Compiler?
Related Questions in MEMORY-ALIGNMENT
- How does OpenGL std430 layout align elements in an array?
- Intel classic compiler reports non-unit strided load in simple assignment
- GCC generates unaligned access for ARMv8
- How is Result<T, E> in Rust so fast?
- Win32 Wide-Character String Alignment Requirements
- Arrange layout of a struct to automatically conform to GLSL std140
- Speed Test for Buffer Alignment: IBM's PowerPC results vs. my CPU
- Can I move between contiguous sequences of fields of the same type in a struct using pointer arithmetic without alignof?
- Are 64-byte CPU cache line reads aligned on 64-byte boundaries?
- Understanding reinterpret_cast error with some templated method
- How calculate, aligned, offset, and count, for, linux's, direct, storage io, through `O_DIRECT`
- Does `__attribute((packed))` affect the alignment of other data structures?
- Why misaligned access to locked memory read intermediate value on intel cpu?
- What stride should I use for matrices in CUDA for the fastest possible speed?
- Alignment of array type data member of a heap allocated object
Related Questions in NIBBLE
- Cast variable to nibble in struct
- Convert a 4 bit binary nibble as a string into its hex equivalent value as a string
- What would be faster: Spliting a 64-bit word into 16 nibbles and entering them in S-Boxes or using an entire 64-bit word directly as an entry?
- Change values in a variable based on a conditional value in R
- Usage of nibble in Programming
- Custom 4 bit data type in C#
- How to read only half a byte from a binary file at a time in C?
- Why are binary numbers almost always grouped in 4 bits?
- Do signed nibbles make any sense?
- Can C cope with sub-byte instruction addressing?
- Trying to split byte in a byte array into two nibbles
- Properly bit packing for enum and typedef struct
- Merge 2 integers into 1 byte
- Bytes to Nibbles to Words to Bytes in C#
- How to perform binary operations on a nibble/tetrad in php?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
In C, it is impossible to access data elements in units smaller than 8 bits, as the smallest possible type is
char, which hasCHAR_BITbits, which is 8 at least. Bitfields are an exception, but don't allow pointers to their members; a data-pointer with sub-(8-)byte-precision can not exist in C.However, instructions (and therefore functions) might be stored differently, and function-pointers could have sub-byte-precision. In general, function pointers and data pointers are not interchangeable, so you can not (correctly) store such a function pointer in a
void*pointer. C does not support accessing the machine code anyways, so there would be no support for accessing instructions that have sub-byte-alignment and/or size.Even on platforms with at least byte-instruction size & alignment, function pointers and data pointers might not be interchangeable, as function pointers might be larger or smaller than data pointers (imagine a system with 256 RAM bytes for data, and 64kB flash bytes for program memory). Therefore, C does not guarantee that
void*can point to everything. However, some platforms such as POSIX do explicitly allow this, to allow e.g.dlsym()to work.