public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66578] [F2008] Invalid free on allocate(...,source=a(:)) in block
Date: Wed, 01 Jul 2015 14:24:00 -0000	[thread overview]
Message-ID: <bug-66578-4-axZiCM1mbH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66578-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66578

vehre at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #35806|0                           |1
        is obsolete|                            |

--- Comment #17 from vehre at gcc dot gnu.org ---
Created attachment 35887
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35887&action=edit
Extended version of Mikael's patch

I have encountered some other issues with the patch for 44672 that are not
fixed by Mikael's patch. Using Mikael's patch as a base I could resolve these
issues:

- when the rank in an assignment was decreased (i.e., the rank of the object(!)
on the rhs was greater then the one needed for the assignment, e.q. selecting a
row from a matrix, testcases are allocate_with_source_7/8), 
- twice indirect element addressing (e.q. using a section of a vector of
indices to address elements in a second array, as in the new testcase
allocate_with_source_9.f08 provided by the patch), and
- fixing char_length_8.

In most cases the issues occurred because the offset was not set correctly when
rebasing to one for the lower bound. 

Please have look whether the things to accomplish can be done easier. This
patch bootstraps and regtests fine x86_64-linux-gnu/f21.


  parent reply	other threads:[~2015-07-01 14:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 19:29 [Bug fortran/66578] New: " tkoenig at gcc dot gnu.org
2015-06-17 19:31 ` [Bug fortran/66578] " tkoenig at gcc dot gnu.org
2015-06-17 20:49 ` dominiq at lps dot ens.fr
2015-06-18  9:37 ` vehre at gcc dot gnu.org
2015-06-18 14:32 ` vehre at gcc dot gnu.org
2015-06-18 17:14 ` tkoenig at gcc dot gnu.org
2015-06-18 18:03 ` vehre at gcc dot gnu.org
2015-06-18 18:17 ` mikael at gcc dot gnu.org
2015-06-19  6:24 ` tkoenig at gcc dot gnu.org
2015-06-19  9:06 ` mikael at gcc dot gnu.org
2015-06-19  9:45 ` vehre at gcc dot gnu.org
2015-06-21 19:03 ` mikael at gcc dot gnu.org
2015-06-21 20:11 ` tkoenig at gcc dot gnu.org
2015-06-22 11:29 ` vehre at gcc dot gnu.org
2015-07-01 14:24 ` vehre at gcc dot gnu.org [this message]
2015-07-07 11:10 ` vehre at gcc dot gnu.org
2015-07-09 10:43 ` vehre 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-66578-4-axZiCM1mbH@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).