This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Thu, Jun 05, 2003 at 02:06:17PM -0700, Richard Henderson wrote: > On Thu, Jun 05, 2003 at 10:50:52AM -0700, H. J. Lu wrote: > > But it isn't safe without knowing if a .o file is ABI conforming or not. > > Correct. > > > With my proposal, the .o files generated by ABI conforming > > compiler will have the NT_GNU_PROPETRTY_IA_64_PRESERVE_GP set and > > the linker can use it to detect the possible run-time failure and > > issue a warning. > > All such .o files? Meaning that you'll get Intel and HP and (...) > to change their object file generation? Intel is ok with this. If HP wants to link against gcc generated .o files safely with full optimization, the answer is yes. > > Anyway, for something this platform specific, you might as well use > an e_flags bit. It is no binary compatible. Please keep in mind this only affects .o files, executables and DSOs are ok. It doesn't make senses to ask everyone to upgrade their whole IA64 system just to support the ia64 psABI conforming .o files generated by the new gcc. Here is the updated one to support --execstack/--noexecstack in gas. H.J.
Attachment:
binutils-prop.patch
Description: Text document
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |