Member • Aug 5, 2012
Member • Aug 8, 2012
Member • Aug 8, 2012
No Sir,pawan.kumar123for windows you need a different program(compiler) but with Linux you need different compiler to convert your c code into machine executable code form
Member • Aug 8, 2012
Member • Aug 8, 2012
Member • Aug 9, 2012
Member • Aug 9, 2012
very well C is not suitable to be run on every machines.....sulochana anandis c platform independent?as i think it is.but it is compiler dependend.my statement is right or wrong?
Member • Aug 9, 2012
Member • Aug 11, 2012
No I have read it on THE COMPUTER ACTIVE magazine an year agosulochana anandi just wan to ask did u check it?
Member • Mar 25, 2014
This discussion has gone all over the place now..sulochana anandI think it is good discussable point that c is platform independent or not.I read in a book that c is portable.and portable means moovable.its true that on diffrent os it gives diffrent result but slightly diffrent.i think its platform independent.what u say?
Member • Mar 25, 2014
So now getting back to query,, what is it that i'm missing?? Does the GCC runtime differ from OS to OS? Then the question is— what happens during when the C output file is being loaded in memory by the program loader part of the operating system? If there are certain platform runtime routines (dynamic libraries) that run on the specific machine when executing the output (post-build linking)... KEEP IN MIND.. ALL THRU THIS DISCUSSION WE HAVE BEEN TAKING INTO CONSIDERATION THE SAME CPU ARCHITECTURE..So pls don't say "it is due to differences in architecture"..RahulbsbThis discussion has gone all over the place now..
Here's my question––
If u write a C program using all the standard C libraries that are common to all platforms (Be it Unix(any flavor) or Windows)e.g--stdio.h or math.h or string.h or stdlib.h and so on..and compile it using a standard compiler (lets take gcc for this discussion's sake) and run it on any one standard CPU arch (X86 for instance 64 bit) why wouldn't the same binary run across different machines matching all the above criteria? e.g when i compile a c code (making use of standard libraries--stdio,stdlib etc) using gcc on my mac (having X86 arch) and create a binary file, shouldn't it be capable of running the bin file on a linux or windows running on an X86 machine (same as my mac's) using the very same gcc runtime.. I'm not using any mac specific C library function or routine that triggers Mac OS specific system calls (i use standard C libs—stdio.h or stdlib.h ) that would become unrecognized in a differing platform.. During the build process of this binary (comprising— preprocessing, compilation,generating assembly code which assembles into object code and then finally standard C built-in library .o files linking with my main.o) there has been no platform specific library used that would do any platform specific system calls or propreitary API used. What i'm getting at is that in order for building the C binary, i have used a common gcc compiler, a common microprocessor arch, and no platform specific system calls (e.g.#including Linux's sys/io.h in a C source file wouldn't even compile on any non linux based box let alone running it.. The compiler will throw a fit on Mac OS or Windows as it won't be able to locate and resolve sys/io.h )
