![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
-
Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Programming for RISC and CISC.
- Thread starter Order
- Start date
Order said:What is/are the language(s) used in programming instruction sets for RISC and CISC processors from either the ground up or modifying the code within existing architectures? Fortran?
There are C compilers which target x86, IA64, MIPS, ARM, etc...
So there is not necessarily a language difference for different processors, unless you're doing assembly. What matters more is the OS or environment that is running on that processor. Programming for a Windows PC, a palm, a smartphone and a heart monitor are all different (usually).
Same answer as above. The vast majority of code is written in high-level languages that are, at the core, platform independent (until you get to OS/Platform APIs). Even compilers are, after a basic core implementation, often written in the language they compile.
Order said:What, then, are the languages used to write for MS x86 servers and IBM/AIX P5 servers?
I don't have access to IBM's source trees. So I can't comment on that.
I don't have access to the Windows source trees either. The below is just based on general programming knowlege.
For the most part, the hardware matters little when writing application code. After all its not like the application source code runs on the hardware, thats where the compiler comes in. Source code is just a way or representing what you want done, its up to the compiler to translate that source code into an executable image which is compatible with the available instruction set and which is loadable by the existing software on the system (the OS, or whatever preexisting system is in place).
Of course, a given platform may have limited compilers available, and no two compilers are exactly the same. Granted though, the lower level you go, the more hardware restricts coding options.
Back in college I did some programming for other systems, there were some Motorola embedded systems and a couple of the early http://netburner.com/ systems. We used C\C++ for everything, no matter what the underlying hardware.
Anyway, as for real world projects
The old version of Windows NT that ran on PowerPC? Id think that >95% of the source was shared with the x86 version, if not more. But again, this is just a guess, I dont have any special insight into the Windows projects, especially one that old.