The message serialization code, as I recall, had problems in making the 64-bit port where two types that were previously separate ended up typedef'ing to the same underlying type. I think Dean removed all of those to make the 64-bit port work now, but that may have the consequence that code that writes, say, a size_t from 64-bit and reads a size_t on 32-bit may disagree about how many bytes to read.
But maybe you don't need all of that code. On Fri, Aug 28, 2009 at 3:44 PM, Mark Wang<[email protected]> wrote: > Hi all, > > Has anyone tried to build the Chromium IPC/shared memory code on 64-bit Mac > OS? We have a need for IPC and shared memory between 64-bit and 32-bit > processes, and what Chrome has seems to be a good fit for our needs. From > my first glance through the code, it looks like standard POSIX without any > obvious bit-width dependencies but I haven't tried it out yet, and it seems > 64-bit Linux is already running on a basic level. > > Is anyone aware of any obvious issues in the 64-bit Mac world? > > Thanks! > > Mark > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
