public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "domob at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49885] [4.6/4.7 Regression] Segmentation fault when writing to an automatic character array
Date: Tue, 02 Aug 2011 20:11:00 -0000	[thread overview]
Message-ID: <bug-49885-4-VYGnw4iN5W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49885-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Daniel Kraft <domob at gcc dot gnu.org> 2011-08-02 20:10:17 UTC ---
Author: domob
Date: Tue Aug  2 20:10:13 2011
New Revision: 177211

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177211
Log:
2011-08-02  Daniel Kraft  <d@domob.eu>

    PR fortran/49885
    * trans-array.c (gfc_trans_auto_array_allocation): Change
    gfc_start_block to gfc_init_block to avoid spurious extra-scope.

2011-08-02  Daniel Kraft  <d@domob.eu>

    PR fortran/49885
    * gfortran.dg/auto_char_dummy_array_3.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/auto_char_dummy_array_3.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-array.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-08-02 20:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 10:58 [Bug libfortran/49885] New: " mathewc at nag dot co.uk
2011-07-28 12:52 ` [Bug libfortran/49885] [4.6/4.7 Regression] " burnus at gcc dot gnu.org
2011-07-28 12:59 ` [Bug fortran/49885] " burnus at gcc dot gnu.org
2011-07-28 14:03 ` burnus at gcc dot gnu.org
2011-07-28 14:07 ` burnus at gcc dot gnu.org
2011-07-28 14:40 ` domob at gcc dot gnu.org
2011-07-29 17:00 ` domob at gcc dot gnu.org
2011-08-01 14:45 ` rguenth at gcc dot gnu.org
2011-08-02 17:55 ` domob at gcc dot gnu.org
2011-08-02 20:11 ` domob at gcc dot gnu.org [this message]
2011-08-02 20:15 ` domob at gcc dot gnu.org
2011-08-03  9:37 ` domob at gcc dot gnu.org
2011-08-03  9:42 ` domob 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-49885-4-VYGnw4iN5W@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).