Displaying 3 results from an estimated 3 matches for "lbss".
Did you mean:
bss
2020 Mar 20
2
RISC-V LLVM sync-up call 19 Mar 2020
...unlimited.
Actually, the global data area, which includes the GOT and any global of local scope, is limited to 4GiB. However, the latter is limited to 2GiB, in order to guarantee addressing the GOT and the small data area, assuming this section order:
1. .got
2. .sdata .sbss
3. .ldata .lbss
The .data and .bss sections, containing the globals of global scope, may follow these immediately, but can actually be placed anywhere in the memory map.
It took me multiple times reading through the proposal to parse that out; it might be a good idea to reorganize the proposal so that’s explain...
2020 Mar 23
2
RISC-V LLVM sync-up call 19 Mar 2020
...ally, the global data area, which includes the GOT and any global of local scope, is limited to 4GiB. However, the latter is limited to 2GiB, in order to guarantee addressing the GOT and the small data area, assuming this section order:
>> • .got
>> • .sdata .sbss
>> • .ldata .lbss
>>
>> The .data and .bss sections, containing the globals of global scope, may follow these immediately, but can actually be placed anywhere in the memory map.
>>
>>
>> It took me multiple times reading through the proposal to parse that out; it might be a good idea...
2020 Mar 20
2
RISC-V LLVM sync-up call 19 Mar 2020
If I’m following correctly, there are two size-limited areas. One area, limited to 2GB, is the “text” area. This contains all the code. Then there’s a “global” area, limited to 4GB, which is pointed to by the global pointer. This contains the GOT, plus a flexible area that the object file can stick small bits of data into. And then outside of both of those, additional data is unlimited.
It