As a temporary work around I simply redefined SYSBASE to 1GB which means my modules are all within the 2GB limit. I'm not sure I want to go the gcc route: I'd rather not introduce another flag etc. Can you think of why GOT/PLT support within krtld is a bad idea? The effort in Linux is minimal. The difficulty I see is allocating the GOT/PLT in storage near to the executable and making sure it's the correct size (e.g. allocate a page and expand as needed).
Neale On Sun, 2007-04-01 at 15:05 -0700, Michael Shapiro wrote: > It is relatively easy to control such mappings (we do similar things > on SPARC): kobj_vmem_init() just has to set up the arenas appropriately > and then all of the module text and data will come from predefined > regions of the address space as determined by the arenas. _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
