[chromium-dev] Re: Chromium IPC layer in 64-bit MacOS

2009-08-31 Thread eZar

Someone runs Chromium 64bits in MAC OS X?
I want to try in Snow Leopard!
Regards,

On Aug 29, 1:02 am, Evan Martin e...@chromium.org wrote:
 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 Wangm...@cooliris.com 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: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---



[chromium-dev] Re: Chromium IPC layer in 64-bit MacOS

2009-08-28 Thread Adam Langley

On Fri, Aug 28, 2009 at 3:44 PM, Mark Wangm...@cooliris.com wrote:
 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.

There is almost no OS X specific code in /ipc and it works on 64-bit
Linux. There is a very high probability that it'll work just fine on
64-bit OS X.


AGL

--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---



[chromium-dev] Re: Chromium IPC layer in 64-bit MacOS

2009-08-28 Thread Jeremy Moskovich
Hi Mark,
We haven't specifically tested the ipc layer as a method to communicate
between 64  32-bit processes on OS X.

At it's core the IPC layer just consists of a pipe to which we read  write
binary data, therefore if the binary representation of the data types that
you want to push over the ipc channel are compatible between both processes,
you *should* be fine.

I don't know what your use case is, but one concern I would have is passing
file descriptors back and forth, while this should work it's untested.

Best regards,
Jeremy

On Fri, Aug 28, 2009 at 3:44 PM, Mark Wang m...@cooliris.com 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: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---



[chromium-dev] Re: Chromium IPC layer in 64-bit MacOS

2009-08-28 Thread Evan Martin

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 Wangm...@cooliris.com 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: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---