[ofw] WDK build environment migration thoughts

[Fab Tillier]

The __ptr64 sign extension happened with the DDK too - so why is it suddenly an issue?  Is it because 32-bit apps running on a 64-bit OS get a lot of pointers with the MSb set?

-Fab

From: ofw-bounces at lists.openfabrics.org [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Alex Naslednikov
Sent: Wednesday, April 30, 2008 9:47 AM
To: Sean Hefty; Smith, Stan; Ishai Rabinovitz
Cc: ofw at lists.openfabrics.org
Subject: RE: [ofw] WDK build environment migration thoughts

Yes, and our solution was dedicated to fix this problem as well.
Currently, it should not work (and I tested it - it indeed doesn't work) because of __ptr64 problem.
This problem was described in details in my previous e-mails because of signed pointer extension.

XaleX

________________________________
From: Sean Hefty [mailto:sean.hefty at intel.com]
Sent: Wednesday, April 30, 2008 5:02 PM
To: Alex Naslednikov; Smith, Stan; Ishai Rabinovitz
Cc: ofw at lists.openfabrics.org
Subject: RE: [ofw] WDK build environment migration thoughts

Also, I'd like to point your attention, that these modules will work as is on homogeneous systems (x86, x64), but not on mixed systems (x86 application on x64 kernel)

Do you know why this does not work?  I would list fixing this as a requirement before the next release.  (Shouldn't be too hard, I would guess.)

Also, I'm assuming based on previous discussions that this does break the ABI.  I never saw any response to my mail that this caused anyone any heartaches, but we should number the July release 2.0, versus 1.2.

- Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20080430/3207cd14/attachment.html>