Thanks for the quick reply, Anton. We have done some cursory tests of a
64-bit client against our 32-bit server implemention. At face-value, it
appears to work. We plan to do more testing of 32/64-bit clients against
our server and will report any findings.
========================================
Mike Helles
140 Canal View Blvd.
Rochester, New York 14623-2808, USA
Phone: (585) 784-7266, Fax: (585) 256-0791
Email: [email protected], Web: www.pt.com
========================================
"Anton Pak" <[email protected]>
07/13/2012 03:01 PM
To
[email protected], "Mike Helles" <[email protected]>
cc
Subject
Re: [Openhpi-devel] Mix of 32/64-bit Client/Server
Hello Mike,
I traced that text section to 2.0 release (that was 7 years ago).
Seems nobody notice it since then.
Doubt there is a man who remembers the real reason for that warning.
We definitely shall rewrite it! :)
There are two known places for possible issue:
- RPC message header is not exactly cross-platform
(Hope to fix it in 3.2.0)
- SaHpi.h and marshal.h define 8/16/32/64 integer as char, short, int,
long long.
Which is true to most platforms.
(Hope to fix it in 3.2.0 too. However it can be tricky on Windows.)
I tried mixing x86, ARM, MIPS32, PPC32 and x86_64 without any issues.
However I haven't tried Itanuim or PPC64.
Could you try running openhpid and a client if you have 32 and 64
hardware?
Anton Pak
On Fri, 13 Jul 2012 22:08:31 +0400, Mike Helles <[email protected]> wrote:
> Hello. According to release notes, you cannot mix 32 and 64-bit
> architectures between an OpenHPI client and server. See below;
>
> ======================================================================
>
> General Information
> -------------------
>
> The client and the daemon do not have to be on the same hardware
> architecture.
> The daemon could be running on a P-series processor and the client
> running
> on an
> x86-series processor. The client library and daemon use a marshaling
> technique
> to resolve architecture and structure padding conflicts. The user does
> not
> need
> to concern themselves with architectureal differences between the client
> and
> daemon. The one exception to this rule is 64-bit architectures. The
> client
> and
> daemon currently cannot resolve differences between 32-bit and 64-bit
> architectures. DO NOT MIX THESE TYPES OF ARCHITECTURES!
>
> ========================================================================
>
> Can someone verify that this is still the case, and if so, is there any
> plan to allow a mix in the future? Can someone provide a detailed
> description of the problem?
>
> Thanks.
> ========================================
> Mike Helles
> 140 Canal View Blvd.
> Rochester, New York 14623-2808, USA
>
> Phone: (585) 784-7266, Fax: (585) 256-0791
> Email: [email protected], Web: www.pt.com
> ========================================
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
