I have installed gcc on many systems and never encountered a problem outside. Having the right compiler may or may not solve your problem, but it won't affect anything that has already run on that box.
For the very unlikely case that you do have problems: install gcc in the form of the lpp-file (from bullfreeware.com) and do not "commit" the software when installing. Until you "commit" in in installp a copy of every overwritten file is saved, committing it will remove that copy. So if you encounter problems you can uninstall the software and have the machine restored to the exact state it was in before the installation.
Download the .bff-file from the mentioned Bull-website. Put it into a directory. Create a .toc-file by making this directory your current directory and issuing the command
inutoc .
call SMITty then:
smitty install_latest
and use "." as your "input directory". Do NOT select "commit software". If you issue an "lslpp -l" you should now see the package in the status of "APPLIED" and not in "COMMITTED".
On how to uninstall a package in an applied state consult your either man ("man installp") or the info-system. Basically it is "installp -u ...". You can do it using SMIT too using the fastpath "smitty install".
Be sure to commit the software in a second step after sufficient testing as this will free up some diskspace. Take your time though, the usability of the software is the same in applied and committed state, so users won't notice.
A Unix system needs a reboot only when a new kernel image needs to be loaded. Reasons for wanting to load a new kernel image would be:
loading a new version of the kernel itself (after patching)
clearing up some NFS-troubles which can't be resolved
clearing the process table to get rid of zombies and the like
and some other reasons. You do NOT need to reboot to change your environment, create a new network interface, add a user and some similar reasons why a certain popular graphical PC-virus needs to be rebooted.
Basically the difference is that in APPLIED state save copies of the files overwritten during install are stored whereas during the transition from APPLIED to COMMIT these save copies are being deleted. Hence, after COMMITting the software it is still possible to deinstall it, but not possible to get the last state before the install back.