From: Francois-Xavier Coudert Date: Mon, 30 Apr 2007 07:54:41 +0000 (+0200) Subject: trouble.texi (Interoperation): Remove note about Ultrix Fortran compiler. X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a19632d4f9784213e1fb50d04ac8c65263437916;p=platform%2Fupstream%2Fgcc.git trouble.texi (Interoperation): Remove note about Ultrix Fortran compiler. * doc/trouble.texi (Interoperation): Remove note about Ultrix Fortran compiler. From-SVN: r124292 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 7a8ce0b..24ff412 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2007-04-30 Francois-Xavier Coudert + + * doc/trouble.texi (Interoperation): Remove note about Ultrix + Fortran compiler. + 2007-04-29 Zdenek Dvorak PR rtl-optimization/31676 diff --git a/gcc/doc/trouble.texi b/gcc/doc/trouble.texi index 505f821..059d5cf 100644 --- a/gcc/doc/trouble.texi +++ b/gcc/doc/trouble.texi @@ -234,20 +234,6 @@ you cannot successfully use @samp{$} in identifiers on the RS/6000 due to a restriction in the IBM assembler. GAS supports these identifiers. -@cindex VAX calling convention -@cindex Ultrix calling convention -@item -@opindex fcall-saved -On Ultrix, the Fortran compiler expects registers 2 through 5 to be saved -by function calls. However, the C compiler uses conventions compatible -with BSD Unix: registers 2 through 5 may be clobbered by function calls. - -GCC uses the same convention as the Ultrix C compiler. You can use -these options to produce code compatible with the Fortran compiler: - -@smallexample --fcall-saved-r2 -fcall-saved-r3 -fcall-saved-r4 -fcall-saved-r5 -@end smallexample @end itemize @node Incompatibilities