<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: 32 bit applications in general in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516973#M870859</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;32 bit apps will talk to a 64 bit app directly providing that the 64 bit app will accept data in 32 bit chunks, the limitations mainly are that the 64 bit applications will be slower.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Paula</description>
    <pubDate>Sat, 14 Apr 2001 16:02:04 GMT</pubDate>
    <dc:creator>Paula J Frazer-Campbell</dc:creator>
    <dc:date>2001-04-14T16:02:04Z</dc:date>
    <item>
      <title>32 bit applications in general</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516972#M870858</link>
      <description>1- Can a 32 bit app talk to a 64 bit APP? If yes, what are the limitations?&lt;BR /&gt;&lt;BR /&gt;2- Do all 32 bit apps are limited to the same space in terms of virtual memory?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Apr 2001 15:44:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516972#M870858</guid>
      <dc:creator>ASOEASTGEOGRAPHY</dc:creator>
      <dc:date>2001-04-13T15:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: 32 bit applications in general</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516973#M870859</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;32 bit apps will talk to a 64 bit app directly providing that the 64 bit app will accept data in 32 bit chunks, the limitations mainly are that the 64 bit applications will be slower.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Sat, 14 Apr 2001 16:02:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516973#M870859</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2001-04-14T16:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: 32 bit applications in general</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516974#M870860</link>
      <description>32 bit and 64 bit apps can communicate through standard methods (shared memory, message queues, memory mapped files, ect). But a 32 bit app cannot access any data elements beyond 32 bit limitations. For instance, shared memory in 64 bit can be up to 8,000 Gbytes in size.&lt;BR /&gt;&lt;BR /&gt;Also, the default data model is slightly incompatible for long and pointer (32 vs. 64 bits).  Now if the defining application is 32 bits, then a 64 bit program would have access to the data but unless explicitly overridden, longs and pointers would mismatch. Thus, the programmer must explicitly code for 32 bit comptibility.&lt;BR /&gt;&lt;BR /&gt;As far as speed differences, that is very difficult to compare. Significant rewrites of some libraries for 64 bit implementations are significantly faster, so the code will run much faster with certain calls. But in general, the difference isn't a lot.  64 bits virtually eliminates addressing limitations (for now). Be sure to look at the Software Transition Kit at:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.software.hp.com/STK/" target="_blank"&gt;http://www.software.hp.com/STK/&lt;/A&gt;</description>
      <pubDate>Sat, 14 Apr 2001 23:44:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/32-bit-applications-in-general/m-p/2516974#M870860</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-04-14T23:44:58Z</dc:date>
    </item>
  </channel>
</rss>

