public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/57079] [Fortran-dev] version/type/attribute fields not set with CLASS components Date: Sat, 22 Mar 2014 19:17:00 -0000 [thread overview] Message-ID: <bug-57079-4-4xNIDcDOl9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57079-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57079 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2014-03-22 Ever confirmed|0 |1 --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- What is the problem with this pr? The difference between the dump with trunk (r208766) and the dev branch (r208422) is --- pr57079.f90.003t.original 2014-03-22 20:11:30.000000000 +0100 +++ pr57079.f90_dev.003t.original 2014-03-22 20:10:59.000000000 +0100 @@ -14,28 +14,38 @@ foo () try { x = 0B; - if (x != 0B) + if ((logical(kind=4)) __builtin_expect ((integer(kind=8)) (x != 0B), 0)) { _gfortran_runtime_error_at (&"At line 10 of file pr57079.f90"[1]{lb: 1 sz: 1}, &"Attempting to allocate already allocated variable \'%s\'"[1]{lb: 1 sz: 1}, &"x"[1]{lb: 1 sz: 1}); } else { - x = (struct t *) __builtin_malloc (112); - if (x == 0B) + x = (struct t *) __builtin_malloc (128); + if ((logical(kind=4)) __builtin_expect ((integer(kind=8)) (x == 0B), 0)) { _gfortran_os_error (&"Allocation would exceed memory limit"[1]{lb: 1 sz: 1}); } } - x->x.data = 0B; - x->y._data.data = 0B; + x->x.base_addr = 0B; + x->x.elem_len = 4; + x->x.version = 1; + x->x.rank = 1; + x->x.type = 1025; + x->x.attribute = 2; + x->y._data.base_addr = 0B; + x->y._data.elem_len = 0; + x->y._data.version = 1; + x->y._data.rank = 1; + x->y._data.type = -1; + x->y._data.attribute = 1; { struct t t.0; if (x != 0B) goto L.1; - x = (struct t *) __builtin_calloc (1, 112); + x = (struct t *) __builtin_calloc (1, 128); L.1:; - t.0.x.data = 0B; - t.0.y._data.data = 0B; + t.0.x.base_addr = 0B; + t.0.y._data.base_addr = 0B; t.0.y._vptr = (struct __vtype_foo_T2 * {ref-all}) &__vtab_foo_T2; t.0.z = 55; *x = t.0; @@ -45,20 +55,20 @@ foo () { if (x != 0B) { - if (x->x.data != 0B) + if (x->x.base_addr != 0B) { - __builtin_free ((void *) x->x.data); + __builtin_free ((void *) x->x.base_addr); } - x->x.data = 0B; - if ((struct t2[0:] * restrict) x->y._data.data != 0B && x->y._vptr->_final != 0B) + x->x.base_addr = 0B; + if ((struct t2[0:] * restrict) x->y._data.base_addr != 0B && x->y._vptr->_final != 0B) { x->y._vptr->_final (&x->y._data, (integer(kind=8)) x->y._vptr->_size, 1); } - if (x->y._data.data != 0B) + if (x->y._data.base_addr != 0B) { - __builtin_free ((void *) x->y._data.data); + __builtin_free ((void *) x->y._data.base_addr); } - x->y._data.data = 0B; + x->y._data.base_addr = 0B; __builtin_free ((void *) x); } }
next prev parent reply other threads:[~2014-03-22 19:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-26 7:37 [Bug fortran/57079] New: " burnus at gcc dot gnu.org 2013-04-26 7:46 ` [Bug fortran/57079] " burnus at gcc dot gnu.org 2014-03-22 19:17 ` dominiq at lps dot ens.fr [this message] 2021-12-18 2:37 ` pinskia 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-57079-4-4xNIDcDOl9@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).