public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35059] Seg fault when max constructor limit reached
Date: Fri, 29 Feb 2008 22:51:00 -0000	[thread overview]
Message-ID: <20080229225114.5904.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35059-10743@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jvdelisle at gcc dot gnu dot org  2008-02-29 22:51 -------
Subject: Bug 35059

Author: jvdelisle
Date: Fri Feb 29 22:50:25 2008
New Revision: 132782

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132782
Log:
2008-02-29  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

        PR fortran/35059
        * expr.c (find_array_element): Modify traversing the constructor to
        avoid trying to access NULL memory pointed to by next for the
        last element. (find_array_section): Exit while loop if cons->next is
        NULL.
        * trans-expr.c (gfc_conv_scalar_char_value): Initialize gfc_typespec.
        (gfc_conv_function_call): Same.
        * decl.c (gfc_match_implicit): Same.
        * trans-intrinsic.c (gfc_conv_intrinsic_sr_kind): Same.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/decl.c
    trunk/gcc/fortran/expr.c
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/fortran/trans-intrinsic.c


-- 


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


  parent reply	other threads:[~2008-02-29 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 17:28 [Bug fortran/35059] New: " jvdelisle at gcc dot gnu dot org
2008-02-02 17:37 ` [Bug fortran/35059] " jvdelisle at gcc dot gnu dot org
2008-02-03 16:33 ` jvdelisle at gcc dot gnu dot org
2008-02-29 22:51 ` jvdelisle at gcc dot gnu dot org [this message]
2008-03-12  1:11 ` jvdelisle at gcc dot gnu dot 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=20080229225114.5904.qmail@sourceware.org \
    --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).