> Phillip Helbig---remove CLOTHES to reply
> wrote:
>
>

>>In article <1inifpp.1j92xdij344rcN%%nospam@see.signature>,
>>nospam@see.signature (Richard Maine) writes:
>>
>>

>>>Phillip Helbig---remove CLOTHES to reply
>>> wrote:
>>>
>>>

>>>>Shouldn't porting (the compiler) it be trivial? That is, just compile and
>>>>go? Or is not everything implemented in the source code of the compiler,
>>>>but instead makes use of system calls etc?

>>>
>>>Um. Compile with what? Yes, after you have a compiler, you can use it to
>>>compile the compiler. Boostrapping cam be decidedly non-trivial. THat's
>>>the whole point, which it looks like you missed.

>>
>>I was thinking a) it is written in C and b) I have a normal C compiler.

>
>
> Sometimes. Not always. Apparently you overlooked the
>
>

>>>>>as far as I know, the
>>>>>available version of the gnu C compiler is too old

>
>
> Which was in the para that you replied to with the comment that porting
> should be trivial.
>
>

>>Apropos.... Isn't the possibility of cross-compilation the reason some
>>things are not allowed by the Fortran standard, while there is no
>>"obvious" reason they should be disallowed?

>
>
> Yes, that reason has been cited in the past. However, it doesn't seem to
> be considered much of a problem any more, so some of those restrictions
> have been lifted. Cross compilation is still needed on occasion, but
> cross compilers today generally have more capability. For example, there
> was concern in the past about cross compilers having to do things like
> implement all the intrinsics twice - once for the target environment and
> once for the compilation environment. That concern contributed towards
> keeping the list of intrinsics allowed in initialization expressions
> down. Today, I think the assumption is that if such duplication is
> needed, it can be done. Resources in the compilation environment are not
> likely to be as shot as they previously might have been. In fact,
> compilation environments for cross compilers are typically fairly "rich"
> environments and often include things such as software emulators for the
> target.
>