public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: sgk@troutmask.apl.washington.edu
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: fix passing of optional dummies to bind(c) procedures [PR113866]
Date: Tue, 13 Feb 2024 19:13:31 +0100	[thread overview]
Message-ID: <93681591-f729-42ee-ab4e-368f01ddc6ae@gmx.de> (raw)
In-Reply-To: <ZculIIjq3DWHEJ3a@troutmask.apl.washington.edu>

Hi Steve,

Am 13.02.24 um 18:21 schrieb Steve Kargl:
> On Mon, Feb 12, 2024 at 09:57:08PM +0100, Harald Anlauf wrote:
>> Dear all,
>>
>> the attached patch fixes a mis-handling of optional dummy arguments
>> passed to optional dummy arguments of procedures with the bind(c)
>> attribute.  When those procedures are expecting CFI descriptors,
>> there is no special treatment like a presence check necessary
>> that by default passes a NULL pointer as default.
>>
>> The testcase tries to exercise various combinations of passing
>> assumed-length character between bind(c) and non-bind(c), which
>> apparently was insufficiently covered in the testsuite.
>>
>> Regtested on x86_64-pc-linux-gnu.  OK for mainline?
>>
>
> Yes.  Thanks for filling out the more detailed testcase.

indeed the new testcase just regressed due to commit
r14-8947-g6caec7d9ec37e6 ... :-(

Reduced testcase which fails on trunk:

program p
   implicit none
   integer, parameter :: n = 100, l = 10
   character(l) :: a = 'a234567890', b(n) = 'bcdefghijk'
   character(:), allocatable :: d, e(:)
   allocate (d, source=a)
   allocate (e, source=b)
   print *, len (d), len (e), size (e)
   call not_bindc_optional_deferred (d, e)
   deallocate (d, e)
contains
   subroutine not_bindc_optional_deferred (c5, c6)
     character(:), allocatable, optional :: c5, c6(:)
     if (.not. present (c5) .or. .not. present (c6)) stop 6
     print *, len (c5), len (c6), size (c6)
     if (len (c5) /= l .or. len (c6) /= l) stop 84
   end
end

Expected:

           10          10         100
           10          10         100

After above commit:

           10          10         100
           10           0         100
STOP 84

Will have to wait until the cause is found and fixed...


  reply	other threads:[~2024-02-13 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 20:57 Harald Anlauf
2024-02-13 17:21 ` Steve Kargl
2024-02-13 18:13   ` Harald Anlauf [this message]
2024-02-13 19:28     ` Harald Anlauf

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=93681591-f729-42ee-ab4e-368f01ddc6ae@gmx.de \
    --to=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).