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/47674] gfortran.dg/realloc_on_assign_5.f03: Segfault at run time
Date: Sat, 12 Feb 2011 19:28:00 -0000	[thread overview]
Message-ID: <bug-47674-4-XDF6lc0cnk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47674-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-02-12 19:24:21 UTC ---
The file was added for PR 47523.

The issue is that there is no temporary generated - but the LHS is dependent on
the LHS. This should only occur for "LHS = LHS(substring)" where no temporary
is needed for the RHS expression but where a reallocation happens. If no
reallocation happens, memmove takes care of possibly overlapping memory. And if
there is a more complicated expression on the RHS, a temporary should always be
present. Thus, the issue should only occur for
  a = a(1:2)
or
  a = (((( a(1:2) ))))


  reply	other threads:[~2011-02-12 19:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  8:43 [Bug fortran/47674] New: " burnus at gcc dot gnu.org
2011-02-12 19:28 ` burnus at gcc dot gnu.org [this message]
2011-08-03  7:24 ` [Bug fortran/47674] gfortran.dg/realloc_on_assign_5.f03: Segfault at run time for deferred (allocatable) string length burnus at gcc dot gnu.org
2013-04-08 20:25 ` tkoenig at gcc dot gnu.org
2013-06-16 20:39 ` dominiq at lps dot ens.fr
2013-09-02 11:18 ` dominiq at lps dot ens.fr
2013-11-23 14:04 ` dominiq at lps dot ens.fr
2014-03-16 10:09 ` tkoenig at gcc dot gnu.org
2014-09-28 21:48 ` bernd.edlinger at hotmail dot de
2014-12-29 17:17 ` tkoenig at gcc dot gnu.org
2015-01-05 17:16 ` tkoenig at gcc dot gnu.org
2015-01-05 19:21 ` tkoenig at gcc dot gnu.org
2015-05-16  6:04 ` tkoenig at gcc dot gnu.org
2015-06-04  9:28 ` tkoenig 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-47674-4-XDF6lc0cnk@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).