- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Global Section Problem of IA64
Operating System - OpenVMS
1752565
Members
5481
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2009 06:57 AM
12-11-2009 06:57 AM
Re: Global Section Problem of IA64
On both platforms, the default extern model is RELAXED_REFDEF
On Alpha the compiler creates storage for a releaxed refdef: an ovr psect. On I64 the compiler creates just a symbol.
On I64 the linker has to check if there is alrady storage for a releaxed refdef symbol. If there is one, the linker uses that storage. If there is none, the linker creates the storage.
On I64, if you mix the extern models, you can end up with a section from one module and a symbol from the other. In the case the section is smaller than the symbol you end up with only the storage from the section.
You can argue that the linker could do better here and a) give a warning or b) create a bigger section. On the other hand, one can argue that the extern model in the application is broken.
With the TMP/HELPER example:
$ cc tmp/extern=common
$ cc helper/extern=relaxed
$ link/map/full tmp,helper
$ search tmp.map "PLGRP_TABLE",GBL/match=and/wind=(0,3)
PLGRP_TABLE 01610000 01619C3F 00009C40 ( 40000.) PAGE 1
6 OVR,REL,GBL,NOSHR,NOEXE, WRT,NOVEC,NOMOD
TMP 01610000 01619C3F 00009C40 ( 40000.) PAGE 1
6
PWASH_QUE_BOT 01619C40 01619C43 00000004 ( 4.) OCTA
4 OVR,REL,GBL,NOSHR,NOEXE, WRT,NOVEC,NOMOD
$
On Alpha the compiler creates storage for a releaxed refdef: an ovr psect. On I64 the compiler creates just a symbol.
On I64 the linker has to check if there is alrady storage for a releaxed refdef symbol. If there is one, the linker uses that storage. If there is none, the linker creates the storage.
On I64, if you mix the extern models, you can end up with a section from one module and a symbol from the other. In the case the section is smaller than the symbol you end up with only the storage from the section.
You can argue that the linker could do better here and a) give a warning or b) create a bigger section. On the other hand, one can argue that the extern model in the application is broken.
With the TMP/HELPER example:
$ cc tmp/extern=common
$ cc helper/extern=relaxed
$ link/map/full tmp,helper
$ search tmp.map "PLGRP_TABLE",GBL/match=and/wind=(0,3)
PLGRP_TABLE 01610000 01619C3F 00009C40 ( 40000.) PAGE 1
6 OVR,REL,GBL,NOSHR,NOEXE, WRT,NOVEC,NOMOD
TMP 01610000 01619C3F 00009C40 ( 40000.) PAGE 1
6
PWASH_QUE_BOT 01619C40 01619C43 00000004 ( 4.) OCTA
4 OVR,REL,GBL,NOSHR,NOEXE, WRT,NOVEC,NOMOD
$
- « Previous
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP