search for: medlow

...have even read only data in ROM. Besides the obvious case of addressing, say, a peripheral buffer in a distant memory location. But the scheme above would not allow 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 <l...

...ly data in ROM. Besides the obvious case of addressing, say, a peripheral buffer in a distant memory location. But the scheme above would not allow 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 Meneze...

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