public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig 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 for deferred (allocatable) string length
Date: Mon, 05 Jan 2015 17:16:00 -0000 [thread overview]
Message-ID: <bug-47674-4-MJrx8cFSBc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47674-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47674
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Mon Jan 5 17:15:17 2015
New Revision: 219193
URL: https://gcc.gnu.org/viewcvs?rev=219193&root=gcc&view=rev
Log:
2015-01-05 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/47674
* dependency.c: Update copyright years.
(gfc_discard_nops): Add prototype.
* dependency.c (discard_nops): Rename to gfc_discard_nops,
make non-static.
(gfc_discard_nops): Use gfc_discard_nops.
(gfc_dep_difference): Likewise.
* frontend-passes.c Update copyright years.
(realloc_strings): New function. Add prototype.
(gfc_run_passes): Call realloc_strings.
(realloc_string_callback): New function.
(create_var): Add prototype. Handle case of a
scalar character variable.
(optimize_trim): Do not handle allocatable variables.
2015-01-05 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/47674
* gfortran.dg/realloc_on_assign_25.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/realloc_on_assign_25.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/dependency.c
trunk/gcc/fortran/frontend-passes.c
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-01-05 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 8:43 [Bug fortran/47674] New: gfortran.dg/realloc_on_assign_5.f03: Segfault at run time burnus at gcc dot gnu.org
2011-02-12 19:28 ` [Bug fortran/47674] " burnus at gcc dot gnu.org
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 [this message]
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-MJrx8cFSBc@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).