Hello All,

I have been in a dilemma to use (-xcode=abs64 -xarch=v9 ) or
(-xcode=pic32 -xarch=v9) to create shared object files for 64-bit
solaris platforms, the manual
(http://docs.sun.com/source/819-3688/cc_ops.app.html#48504) does not
say anything about the programs performance with -xcode=abs64.

-------------
Some questions about PIC

o What is the need ot PIC code in shared object files? (is it just to
share the library between different program instances)??

o We can create shared objects without PIC mode on 32-bit (so OS not
sharing the library for 32-bit program  instances of the executable?)

o Why is that the linker blindly forces that all the code should be
POSITION-INDEPENDENT while creating shared libraries , since my shared
library is very specific to my application and there is only one
instance of the program running at a time, I dont see the need of the
solaris kernel to share my page (shared object) with other instances
of the program.

o on linux machines (X84_64) also 64-bit dynamic shared objects should
be build in -fPIC mode, but I verified that the linker on IA64 just
does the job of creating the dynamic shared objects with out -fPIC
flag. So is it something to do with the processor also?

Which part of the kernel deals with sharing of the shared libraries
across various instances of the program?
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to