1 Feb
2012
1 Feb
'12
3:08 p.m.
ons 2012-02-01 klockan 09:09 -0500 skrev Toby Thain:
Of course, some still wrote code as if "all the
world's VAX," followed
by "all the world's a SPARC," and of course we all know what the world
is now...
That is the environment from which gcc was born. It is still amazing to
me how completely gcc met its original goals, eventually supplanting
major vendor compilers (which many hoped for, but few could have
predicted in the 1980s).
--Toby
GCC = The commissioning engineers jive but for memory.
The anecdote that DEC field engineers danced on SAIL's memory cabinets
to find the wrinkles in her memory banks.
For the case of gcc: a common sw whose deployment is good at finding bit
errors in an PC:s memory. Compile gcc, and have gcc recompile itself at
least four times, if the compile fails mysteriously (for example BUS
ERROR), it is a big probability that the memory is shoot somewhere.
The purpose would be to show myself and others
how un-portable portable
code really is.
I think statement such as "this program is written to be portable" it
means portable in just one or a handfull of aspects.
E.g. "Portable regarding endianess"
"Has been compiled with GCC on two platforms"
/Pontus