public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52044] [OOP] Invalid memory access with ALLOCATE, default initializer and polymorphic array components Date: Mon, 06 Feb 2012 21:24:00 -0000 [thread overview] Message-ID: <bug-52044-4-PRnsDZthMl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52044-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52044 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |pault at gcc dot gnu.org Resolution| |FIXED --- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> 2012-02-06 21:24:12 UTC --- This is now fixed, since __builtin_memset (two.a._data.data, 0, 96); appears after allocation. Thanks for this and all the other extracts from Damian and co.'s book! Cheers Paul
prev parent reply other threads:[~2012-02-06 21:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-29 18:36 [Bug fortran/52044] New: " burnus at gcc dot gnu.org 2012-01-29 20:03 ` [Bug fortran/52044] " burnus at gcc dot gnu.org 2012-02-06 21:24 ` pault 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-52044-4-PRnsDZthMl@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).