This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [doc,patch] Fortran compiler on Ultrix and clobbered registers
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: fxcoudert at gmail dot com (FX Coudert)
- Cc: dave dot anglin at nrc dot ca, matt at 3am-software dot com, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Sun, 29 Apr 2007 13:43:49 -0400 (EDT)
- Subject: Re: [doc,patch] Fortran compiler on Ultrix and clobbered registers
> I noted in the GCC docs (see for example http://gcc.gnu.org/
> onlinedocs/gcc/Interoperation.html) that we have the following text
> in the section "Known Causes of Trouble with GCC":
>
> > 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:
> > -fcall-saved-r2 -fcall-saved-r3 -fcall-saved-r4 -fcall-
> > saved-r5
>
> That code was initially committed to gcc/gcc.texi in 1997 (it's now
> in gcc/doc/gcc.texi). As there have been a few changes on the
> compiler since that time, I wonder if it's still true, and still
> useful to have that comment there. As there is no ultrix maintainer
> (though it's still listed as a supported platform), I'm CCing the VAX
> maintainers: can you comment on the usefulness of this part of the doc?
As far I can tell, the options are still supported and the comment
is accurate.
Whether it's still useful is another matter. Although vax-ultrix
is still nominally supported, there is no remaining interest in this
port. I haven't attempted a build since 4.1. So, I wouldn't object
to your removing this comment.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)