Cuberite Forum
GPU code - Printable Version

+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: GPU code (/thread-1480.html)

Pages: 1 2 3 4 5 6 7


RE: GPU code - LO1ZB - 06-13-2014

May I try to compile it? What would I need for that?


RE: GPU code - tigerw - 06-13-2014

Does GCC crash? We should try to get an online compiler to compile it and see what happens...


RE: GPU code - worktycho - 06-13-2014

I'm trying it now.

gcc just produces massive errors. Here's another reason to use another method: one error results in 121 lines of output.

121 lines may not sound like much but on average each line is 4.5 million chars long.


RE: GPU code - tigerw - 06-13-2014

Uh. What sort of code are you feeding the poor programs?


RE: GPU code - worktycho - 06-13-2014

50-100 nested deep templates.


RE: GPU code - bearbin - 06-13-2014

On average... 4.5 million characters!!!


RE: GPU code - worktycho - 06-15-2014

Since Option 1 on the original post has now been shown to be infeasible what are peoples preferred options? We've now got tolua working automatically on MSVC so that would mean the builds would be simpler for option 2 and 3. Personally my preferred option in option 3 with a lisp.


RE: GPU code - xoft - 06-15-2014

You need to keep in mind that we're supporting Windows, which doesn't seem to have that many languages supported nativelyTongue

I'd go with option 4.


RE: GPU code - worktycho - 06-15-2014

Also the fact that there really isn't a language that has the same support as C++ that provides the features necessary. I was thinking of writing my own lisp compiler. As for option 4 remember what happened with the old SSE generator. And we'd have four or five now.


RE: GPU code - xoft - 06-15-2014

We'd need to rewrite most of the generator code anyway, to use arrays of values and operations over them. It should be fairly easy to make the split happen then.

"An own lisp compiler" sounds like a bad idea, regarding the cross-platform builds such as Android. We don't want to use any self-compiled tools, remember?