public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/49262] 3-yr-old infinite loop in dwarf2out.c
Date: Mon, 04 Jul 2011 21:11:00 -0000	[thread overview]
Message-ID: <bug-49262-4-LIf4RXdySt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49262-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-07-04 21:08:00 UTC ---
Author: jakub
Date: Mon Jul  4 21:07:57 2011
New Revision: 175827

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175827
Log:
    Backported from mainline
    2011-06-06  Jakub Jelinek  <jakub@redhat.com>

    PR debug/49262
    * dwarf2out.c (native_encode_initializer): Decrement count in each
    iteration.

    2011-06-30  Jakub Jelinek  <jakub@redhat.com>

    PR fortran/49540
    * gfortran.h (gfc_constructor): Add repeat field.
    * trans-array.c (gfc_conv_array_initializer): Handle repeat > 1.
    * array.c (current_expand): Add repeat field.
    (expand_constructor): Copy repeat.
    * constructor.c (node_free, node_copy, gfc_constructor_get,
    gfc_constructor_lookup): Handle repeat field.
    (gfc_constructor_lookup_next, gfc_constructor_remove): New functions.
    * data.h (gfc_assign_data_value): Add mpz_t * argument.
    (gfc_assign_data_value_range): Removed.
    * constructor.h (gfc_constructor_advance): Removed.
    (gfc_constructor_lookup_next, gfc_constructor_remove): New prototypes.
    * data.c (gfc_assign_data_value): Add REPEAT argument, handle it and
    also handle overwriting a range with a single entry.
    (gfc_assign_data_value_range): Removed.
    * resolve.c (check_data_variable): Adjust gfc_assign_data_value
    call.  Use gfc_assign_data_value instead of
    gfc_assign_data_value_expr.

    * gfortran.dg/pr49540-1.f90: New test.
    * gfortran.dg/pr49540-2.f90: New test.

Added:
    branches/gcc-4_6-branch/gcc/testsuite/gfortran.dg/pr49540-1.f90
    branches/gcc-4_6-branch/gcc/testsuite/gfortran.dg/pr49540-2.f90
Modified:
    branches/gcc-4_6-branch/gcc/ChangeLog
    branches/gcc-4_6-branch/gcc/dwarf2out.c
    branches/gcc-4_6-branch/gcc/fortran/ChangeLog
    branches/gcc-4_6-branch/gcc/fortran/array.c
    branches/gcc-4_6-branch/gcc/fortran/constructor.c
    branches/gcc-4_6-branch/gcc/fortran/constructor.h
    branches/gcc-4_6-branch/gcc/fortran/data.c
    branches/gcc-4_6-branch/gcc/fortran/data.h
    branches/gcc-4_6-branch/gcc/fortran/gfortran.h
    branches/gcc-4_6-branch/gcc/fortran/resolve.c
    branches/gcc-4_6-branch/gcc/fortran/trans-array.c
    branches/gcc-4_6-branch/gcc/testsuite/ChangeLog


      parent reply	other threads:[~2011-07-04 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 19:25 [Bug c/49262] New: " jim at meyering dot net
2011-06-01 20:37 ` [Bug c/49262] " ebotcazou at gcc dot gnu.org
2011-06-06 16:17 ` [Bug debug/49262] " jakub at gcc dot gnu.org
2011-06-06 17:46 ` jakub at gcc dot gnu.org
2011-06-06 18:03 ` jakub at gcc dot gnu.org
2011-07-04 21:11 ` jakub at gcc dot gnu.org [this message]

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-49262-4-LIf4RXdySt@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).