public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thomas.robinson at noaa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100860] New: class(*) type is (character(*)) produces a segmentation fault when run
Date: Tue, 01 Jun 2021 17:39:37 +0000	[thread overview]
Message-ID: <bug-100860-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100860
           Summary: class(*) type is (character(*)) produces a
                    segmentation fault when run
           Product: gcc
           Version: 11.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: thomas.robinson at noaa dot gov
  Target Milestone: ---

When a string is passed as an argument to a subroutine where the argument is
`class(*)`, there is a seg fault when the type is selected.  Other types seem
to be working.
Previous versions of gfortran have no problem compiling and running this simple
program.  I think the code is correct.  It seems to be gcc 11 that has an
issue.

Here is some test code:

module ctest
contains

subroutine sub (carg, slen)

 class(*), intent (in) :: carg
 integer, optional, intent (in)  :: slen

 select type (carg)
 type is (character(*))
   if (.not.present(slen)) then
     write (6,*) "This is an error dealing with a string"
   else
     write (6,*) "string length is ",slen
     write (6,*) "String is ",carg(1:slen)
   endif

 type is (integer)
   write (6,*) "Integer type is ", carg
 type is (real)
   write (6,*) "Real type is ", carg
 class default
   write (6,*) "Not the right type"
 end select


end subroutine sub


end module ctest

program test

use ctest

character (len=10) :: c10
character (len=:), allocatable :: sall
integer :: i=100
real :: r = 999.9
logical :: l = .true.
 call sub (r)
 call sub (i)
 call sub (l)
 c10="12345"
 allocate(character (len=i) :: sall)
 sall = "87654321"
! write (6,*) "c10=",trim(c10),"::LEN=",len_trim(c10)
! call sub(trim(c10), len_trim(c10))
 write (6,*) "sall=",trim(sall),"::LEN=",len_trim(sall)
 call sub(trim(sall),len_trim(sall))



end program test

Here is the output
 Real type is    999.900024    
 Integer type is          100
 Not the right type
 sall=87654321::LEN=           8

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.


I tried with heap and stack strings, and both fail (you can see I have the
first one commented out).  Please let me know if there's any more information
you need.

             reply	other threads:[~2021-06-01 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 17:39 thomas.robinson at noaa dot gov [this message]
2021-06-01 18:19 ` [Bug fortran/100860] " anlauf at gcc dot gnu.org
2021-06-01 18:38 ` dominiq at lps dot ens.fr
2021-06-02 13:14 ` thomas.robinson at noaa dot gov
2021-06-02 13:16 ` thomas.robinson at noaa dot gov

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-100860-4@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).