Add Windows and MACOS support..

[GoogleCodeExporter]

Now that you have LLVM multicore support working (I don't know if you are
aware of Nvidia similar efforts for CUDA for CPUs..
llvm.org/devmtg/2009-10/Grover_PLANG.pdf
and also they have a video..
 I hope they have ready for CUDA 3.0.. which seems to be getting a beta by
SC09 and hope they release PTX spec v1.5 ) 
Assuming CUDA multicore doesn't get relased in this beta I'm interested in
porting your project to Windows and MacOS assuming it can be done with no
major changes.. I mean getting perhaps rid of configure/automake stuff..
and perhaps some fixing system specific code..
Would be good if with some of your thougt you can point me to some big
issues you can expect me to find and already not planned by me?

So perhaps the plan is:
I will try first to test in MacOs which would allow to catch very specific
Linux issues..
Then from that try to use Cmake as make system..
Assuming all goes well on Linux and MacOs attempt Windows port..
This will expose first two kind of portability issues:
*GCC vs Visual Studio issues: 
are you using some C99 or other specific GCC code don't supported.. 
*OS specific API stuff..
I expect I'm having to learn to build:
Boost..
Pthreads..
LLVM..

Original issue reported on code.google.com by rtf...@gmail.com on 31 Oct 2009 at 10:13

• Merged into: #51

[GoogleCodeExporter]

I have seen the NVIDIA slides, no comment other than that.  Regardless of 
whether or
not they end up releasing PLANG we wanted an open-source framework to 
experiment with
the same problem.  

In terms of adding a windows and macos port of ocelot, obviously supporting
additional platforms would widen the appeal of Ocelot and even CUDA.  However, 
adding
additional platforms always involves increasing the number of test cases and
complicates the code that is platform specific.  If someone is willing to devote
resources to this I think that everyone involved would be grateful and we would 
be
willing to offer suggestions, but probably not anything more than that.  In the 
end
we are using ocelot to explore research into dynamic compilation for many-core
architectures.  Making the code portable and useful to others is helpful, but 
it is
not our primary goal.

For macos, I think someone has tried this before:
http://groups.google.com/group/gpuocelot/browse_thread/thread/035988f46627db1b#

You will definitely run into compiler issues, we have a few problems going from 
one
version of gcc to the next.  

You will run into trouble with linux timers, possibly pthreads, and as you 
mention,
we use C99 and experimental gcc TR1 extensions.

Original comment by gregory....@gatech.edu on 2 Nov 2009 at 9:09

[GoogleCodeExporter]

Added new windows branch in branches/ocelot-windows

Original comment by gregory....@gatech.edu on 26 Aug 2010 at 12:37

• Changed state: Started

[GoogleCodeExporter]

Original comment by gregory....@gatech.edu on 23 Jun 2011 at 10:05

• Changed state: Duplicate