c++ Development on Mac OSX 10.4.11

[HasanRazaKz]

I have developed an application to run on Mac hardware 10.6.8 and 10.4.11, Application is developed in c++ using STL containers like map, vectors extensively.
The problem is, application is running smooth on new hardware that is 10.6.8, but it creates some un-predictable problems on PowerPC hardware. Like execution of for loop never terminates, STL iterator ++ (increment) errors (Code is logically correct and application is tested for same data). Application may generate errors after long interval of time.
I just want to know that if there is some compatibility issue with C++ and PowerPC or anything else I am missing?

 

[chas_m]

PowerPC is dead, and maybe 0.1 percent of active Mac users are still on a system that is PPC only (at least according to Netcraft). If you actually manage to fix this you will be the first developer who has written new software for PPC in at least five years.

What is the point of expending the effort to fix this issue when there is nobody who needs it? You've got it working beautifully in Intel code going back to machines from five years ago -- that is WAY above and beyond the call!

Next you'll be telling me the Amiga version has bugs that are hard to track down, eh?

 

[vansmith]

Application may generate errors after long interval of time.
I just want to know that if there is some compatibility issue with C++ and PowerPC or anything else I am missing?

What kinds of errors?

I'm not sure if this is an issue of the architecture and/or a limitation of OS X 10.4.11. If you create a very basic loop that iterates over an array, for example, do you still have issues on the PPC Mac?

 

[johnodd4]

??? Are you trying to run intel code on a powerpc mac it's never going to work and why tiger no one hardly uses it.

 

[Raz0rEdge]

From a language perspective, there wouldn't be a difference between X86 and PowerPC since the compiler is responsible to handle the generation of the appropriate machine-specific instructions from your code..

So what compilers are you using to compile your code? I would verify basic functionality of the PowerPC compiler as Vansmith suggested with a trivial app..

You might also want to check which C++ specification the PowerPC compiler is using since that matters greatly when it comes to things like STL and so on. If the Standard Template Libraries that were available at the 10.4.x era differ greatly than what is available in the 10.6.8 era, then your code might produce different results based on that...

So start with a basic application and FOR (a primitive) loop and see what happens..

 

[Raz0rEdge]

PowerPC is dead, and maybe 0.1 percent of active Mac users are still on a system that is PPC only (at least according to Netcraft). If you actually manage to fix this you will be the first developer who has written new software for PPC in at least five years.

What is the point of expending the effort to fix this issue when there is nobody who needs it? You've got it working beautifully in Intel code going back to machines from five years ago -- that is WAY above and beyond the call!

Next you'll be telling me the Amiga version has bugs that are hard to track down, eh?

I don't believe the OP asked anyones opinion on WHETHER developing for PowerPC is a good idea or not. They asked about a specific issue related to that architecture. If you have something relevant to add about the question asked, by all means add to the discussion, otherwise there's no need to interject with opinions about how the OP should spend their time..

 

[vansmith]

I wonder if, in part, this has to do with Apple's transition from GCC to LLVM based compilers. I don't know enough about the differences but perhaps if LLVM is used on the Intel machines, perhaps there are issues trying to build with GCC (if libraries, for example, are organized differently).

(I'm really pushing my knowledge of C/C++ here...)