public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/102111] Segfault with associate to derived type with allocatable component
Date: Fri, 27 Aug 2021 22:39:12 +0000 [thread overview]
Message-ID: <bug-102111-4-aXS1cMWdUk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102111-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102111
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to Brad Richardson from comment #0)
> I'm using version Ubuntu 11.1.0-1ubuntu1~21.04 on Pop!OS.
>
> I suspect this is related to 102106, but fails every time instead of just
> intermittently.
>
> program main
> type :: example_t
> integer, allocatable :: vals(:)
> end type
>
> associate(example => example_t([42]))
> end associate
> end program
This appears to be fixed in HEAD. I added
print *, example%vals
within the associate statement. With gfortran 10.someversion, I
get
% gfortran10 -o z a.f90
% ./z
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x80081f6bb in ???
#1 0x80081e876 in ???
#2 0x7ffffffff192 in ???
#3 0x801093fa1 in ???
#4 0x400d8a in ???
#5 0x400e37 in ???
#6 0x40083f in ???
With HEAD, I get
% gfcx -o z a.f90
% ./z
42
next prev parent reply other threads:[~2021-08-27 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 22:08 [Bug libfortran/102111] New: " everythingfunctional at protonmail dot com
2021-08-27 22:39 ` kargl at gcc dot gnu.org [this message]
2021-08-27 22:42 ` [Bug libfortran/102111] " everythingfunctional at protonmail dot com
2021-09-06 20:04 ` anlauf at gcc dot gnu.org
2023-04-08 13:00 ` [Bug fortran/102111] " pault at gcc dot gnu.org
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-102111-4-aXS1cMWdUk@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).