Displaying 3 results from an estimated 3 matches for "cmplow".
2020 Mar 20
2
RISC-V LLVM sync-up call 19 Mar 2020
...code and data to reside in different memory devices, if the user so prefers.
On the other hand, just like we have the code models `medlow` and `medany`, we could have two variations of the compact code model too. One assuming that code and small data and local data are on the same memory device (`cmplow`) and another assuming no such restriction (`cmpany`).
Thank you,
__
Evandro Menezes ◊ SiFive ◊ Austin, TX
From: llvm-dev <llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces at lists.llvm.org>> On Behalf Of Evandro Menezes via llvm-dev
Sent: Thursday, March 19, 2020 9:19 AM...
2020 Mar 23
2
RISC-V LLVM sync-up call 19 Mar 2020
...eside in different memory devices, if the user so prefers.
>>
>> On the other hand, just like we have the code models `medlow` and `medany`, we could have two variations of the compact code model too. One assuming that code and small data and local data are on the same memory device (`cmplow`) and another assuming no such restriction (`cmpany`).
>>
>> Thank you,
>>
>> __
>> Evandro Menezes ◊ SiFive ◊ Austin, TX
>>
>>
>> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Evandro Menezes via llvm-dev
>> Sent:...
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