public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98433] double free detected in tcache 2, after merge of structures Date: Thu, 24 Dec 2020 00:52:46 +0000 [thread overview] Message-ID: <bug-98433-4-EhPlBsxJtS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98433-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98433 --- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Wed, Dec 23, 2020 at 11:29:47PM +0000, guez at lmd dot ens.fr wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98433 > > --- Comment #2 from Lionel GUEZ <guez at lmd dot ens.fr> --- > Sure, the issue goes away if you specify the components. > > When you say "the likely correct line", do you imply that the line without the > components is incorrect? Likely, as in I need to check the Fortran standard for the correct behavior. > I would insist that the line without the components is > correct. See for example Adams, Fortran 2003 Handbook, 2009, section 7.5.2: Don't own that book. In fact, I own no books that cover anything beyond Fortran 95.
next prev parent reply other threads:[~2020-12-24 0:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-23 22:18 [Bug fortran/98433] New: " guez at lmd dot ens.fr 2020-12-23 22:43 ` [Bug fortran/98433] " kargl at gcc dot gnu.org 2020-12-23 23:29 ` guez at lmd dot ens.fr 2020-12-24 0:52 ` sgk at troutmask dot apl.washington.edu [this message] 2020-12-24 7:55 ` guez at lmd dot ens.fr 2020-12-24 12:01 ` anlauf at gcc dot gnu.org 2020-12-24 19:31 ` kargl at gcc dot gnu.org 2020-12-24 23:03 ` guez at lmd dot ens.fr 2023-07-23 19:12 ` anlauf 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-98433-4-EhPlBsxJtS@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: linkBe 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).