public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56596] Invalid read of size 4 gfortran.dg/class_array_7.f03
Date: Fri, 28 Jun 2013 07:10:00 -0000	[thread overview]
Message-ID: <bug-56596-4-StV49vKsyF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56596-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56596

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
                 CC|                            |burnus at gcc dot gnu.org
         Resolution|---                         |FIXED

--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to janus from comment #1)
>   allocate (extended_type :: a(2))
> a._data.data = (void * restrict) __builtin_malloc (8);
> 
> The allocation size seems to be independent of whether one allocates with
> "base_type" or "extended type".

(In reply to Dominique d'Humieres from comment #3)
> This seems to have been fixed [...] revision 199528?

Yes, it has been fixed by the patch for PR57456, r199528

-> Close as FIXED.


  parent reply	other threads:[~2013-06-28  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 13:54 [Bug fortran/56596] New: " dominiq at lps dot ens.fr
2013-03-13 14:18 ` [Bug fortran/56596] " janus at gcc dot gnu.org
2013-06-27 10:00 ` dominiq at lps dot ens.fr
2013-06-27 21:46 ` dominiq at lps dot ens.fr
2013-06-28  7:10 ` burnus at gcc dot gnu.org [this message]
2013-06-29 22:07 ` dominiq at lps dot ens.fr
2013-06-30 15:25 ` dominiq at lps dot ens.fr

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