public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/101305] Bind(C): Problems with incorrect kinds/sizes in ISO_Fortran_binding.h and CFI_establish
Date: Tue, 10 Aug 2021 15:27:05 +0000	[thread overview]
Message-ID: <bug-101305-4-AHzoYcohl8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101305-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101305

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:2ba0376ac40447ce7ee09fcef00511c18db25dfa

commit r12-2839-g2ba0376ac40447ce7ee09fcef00511c18db25dfa
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Tue Aug 10 17:26:32 2021 +0200

    gfortran: Fix in-build-tree testing [PR101305, PR101660]

    ISO_Fortran_binding.h is written in the build dir - hence, a previous
commit
    added it as include directory for in-build-tree testing.  However,
    it turned out that -I$specdir/libgfortran interferes with reading .mod
files
    as they are then no longer regareded as intrinsic modules.  Solution:
Create
    an extra include/ directory in the libgfortran build dir and copy
    ISO_Fortran_binding.h to that directory.  As -B$specdir/libgfortran already
    causes gfortran to read that include subdirectory, the -I flag is no longer
    needed.

            PR libfortran/101305
            PR fortran/101660
            PR testsuite/101847

    libgfortran/ChangeLog:

            * Makefile.am (ISO_Fortran_binding.h): Create include/ in the build
dir
            and copy the include file to it.
            (clean-local): Add for removing the 'include' directory.
            * Makefile.in: Regenerate.

    gcc/testsuite/ChangeLog:

            * lib/gfortran.exp (gfortran_init): Remove -I$specpath/libgfortran
            from the string used to set GFORTRAN_UNDER_TEST.

      parent reply	other threads:[~2021-08-10 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  5:48 [Bug libfortran/101305] New: " sandra at gcc dot gnu.org
2021-07-06 20:11 ` [Bug libfortran/101305] " sandra at gcc dot gnu.org
2021-07-08 19:03 ` sandra at gcc dot gnu.org
2021-07-14  0:08 ` sandra at gcc dot gnu.org
2021-07-28  4:24 ` cvs-commit at gcc dot gnu.org
2021-07-28  4:24 ` cvs-commit at gcc dot gnu.org
2021-07-28  4:24 ` cvs-commit at gcc dot gnu.org
2021-07-28 20:21 ` sandra at gcc dot gnu.org
2021-08-09 10:36 ` cvs-commit at gcc dot gnu.org
2021-08-10 15:27 ` cvs-commit at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101305-4-AHzoYcohl8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).