search for: daarri

Implementing the backend (or editing the current PPC backend as needed) is a definite option. This seems to be the real question... which is easier... maintaining the PPC backend or maintaining the rewriter. Currently (in admittedly trivial tests) I have gotten the rewriter to work and output C code. There are some outstanding issues to do with linking and accessing the reflection information

By linux derivative I meant that it borrows the linux GCC ABI... and it does. You can compile with an off the shelf GCC cross compiler and link the resultant object files ones compiled with the PS3 provided version. We have done it. Also, as both an XBox 360 and PS3 developer, there seems to me to be nothing in the TCRs/TRCs that preclude us from using a different compiler. There are rules

Le 27 mai 2010 à 09:15, Kevin Wooten a écrit : > Implementing the backend (or editing the current PPC backend as needed) is a definite option. This seems to be the real question... which is easier... maintaining the PPC backend or maintaining the rewriter. Currently (in admittedly trivial tests) I have gotten the rewriter to work and output C code. There are some outstanding issues to do

PS3 is not "a Linux derivative." The compilers supplied by SCE for PS3 game development are highly customized and support a customized ABI that will take some time to adjust LLVM and Clang to support. You'd likely also run afoul of a TRC or two, similar to the problems you'll face with Microsoft TCRs mentioned earlier. Alex On May 27, 2010, at 12:15 AM, Kevin Wooten

Please create a thread on DevNet to discuss this further. Alex On May 27, 2010, at 9:26 AM, Kevin Wooten wrote: > By linux derivative I meant that it borrows the linux GCC ABI... and > it does. You can compile with an off the shelf GCC cross compiler > and link the resultant object files ones compiled with the PS3 > provided version. We have done it. > > Also, as both

Why? I think the discussion belongs here, and the topic doesn't seem to include proprietary information - a lot of 360 info has been made public through MS material. Other info can be discussed without much disclosure (we can refer to TCRs by three-letter category and number, etc). - Sherief On May 27, 2010, at 1:15 PM, Alex Rosenberg wrote: > Please create a thread on DevNet to discuss

Kevin, there're some unwritten rules on the 360 that seem to interfere with code generation - pointer load-stores seem to require zeroing the most significant 32 bits, for example - that was one issue that I ran into a while ago while fooling around with code generation on the 360 (and don't blame me if I'm slightly off the mark, it was quite a while ago). I didn't seem to find it

llvm can output C code, but that target has bitrotted severely over the last few months and nobody seems to be interested in fixing it. You may need to do some work there. Alternatively you could implement the PPC ABI that you need. There are several examples of supporting multiple ABIs on the same hardware, x86 being the most obvious. A lot of simple stuff will probably Just Work with the

Yep... I have been a 360 developer since the days when it was a actual Macintosh G5. I went to all the early tech. seminars and learned way more about that wacky processor and MS's seemingly crazy ABI choices than I care to (I know, I know, they had their reasons for them). Knowing this is why I quickly turned toward rewriting objc instead of attempting to implement a backend. I have also

We are looking at using Objective-C/C++ in a new game engine.  Objective C's duality of being both very dynamic and very "C" gives us exactly what we need to make the SDK and engineering of games simpler. This means that we will need a way to compile it on all platforms our games will target.  Currently the major platforms we are concerned with include... PC, Mac, XBox 360, PS3,