This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 8.1 Released
- From: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- To: Bert Wesarg <bert dot wesarg at googlemail dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Fri, 4 May 2018 09:31:29 +0300
- Subject: Re: GCC 8.1 Released
- References: <20180502121524.GT8577@tucnak> <CAKPyHN0VKPbHL2_42HJMhr9jagPFaKqsC18AitJS3x1w4+EWPQ@mail.gmail.com>
On Fri, May 4, 2018 at 9:22 AM, Bert Wesarg <bert.wesarg@googlemail.com>
wrote:
> Hi,
>
> On Wed, May 2, 2018 at 2:15 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> > Some code that compiled successfully with older GCC versions might
> require
> > source changes, see http://gcc.gnu.org/gcc-8/porting_to.html for
> > details.
>
> in "Fortran language issues" it reads: "Prior to GCC 7", shouldn't
> that be "Prior to GCC 8" or "Up to GCC 7"?
>
Yes, indeed it should. Thanks for noticing.
>
> And can somebody can tell me, whether this Fortran issue effects also
> Fortran code which calls C functions?
>
>
If it's a "normal" C function with NULL-terminated strings, then no. If
it's a C function which is designed to follow the Fortran procedure ABI
(where strings are passed as a pointer + a hidden length argument), then
yes.
--
Janne Blomqvist