public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34884] [4.3 Regression] gfortran.dg/array_constructor_9.f90
Date: Tue, 22 Jan 2008 14:04:00 -0000	[thread overview]
Message-ID: <20080122135750.32647.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34884-682@http.gcc.gnu.org/bugzilla/>



------- Comment #29 from zadeck at gcc dot gnu dot org  2008-01-22 13:57 -------
Subject: Bug 34884

Author: zadeck
Date: Tue Jan 22 13:57:01 2008
New Revision: 131719

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131719
Log:
2008-01-22  Kenneth Zadeck <zadeck@naturalbridge.com>

        PR rtl-optimization/26854
        PR rtl-optimization/34400
        PR rtl-optimization/34884
        * ddg.c (create_ddg_dep_from_intra_loop_link): Use
        DF_RD->gen.
        * df.h (df_changeable_flags.DF_RD_NO_TRIM): Deleted
        (df_rd_bb_info.expanded_lr_out): Deleted
        * loop_invariant.c (find_defs): Deleted DF_RD_NO_TRIM flag.
        * loop_iv.c (iv_analysis_loop_init): Ditto.  * df-problems.c
        (df_rd_free_bb_info, df_rd_alloc, df_rd_confluence_n,
        df_rd_bb_local_compute, df_rd_transfer_function, df_rd_free):
        Removed code to allocate, initialize or free expanded_lr_out.
        (df_rd_bb_local_compute_process_def): Restructured to make more
        understandable.
        (df_rd_confluence_n): Removed code to no apply invalidate_by_call
        sets if the sets are being trimmed.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/ddg.c
    trunk/gcc/df-problems.c
    trunk/gcc/df.h
    trunk/gcc/loop-invariant.c
    trunk/gcc/loop-iv.c


-- 


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


  parent reply	other threads:[~2008-01-22 13:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20  8:45 [Bug fortran/34884] New: " hjl dot tools at gmail dot com
2008-01-20 11:31 ` [Bug fortran/34884] " dominiq at lps dot ens dot fr
2008-01-20 12:05 ` dominiq at lps dot ens dot fr
2008-01-20 12:22 ` dominiq at lps dot ens dot fr
2008-01-20 13:20 ` dominiq at lps dot ens dot fr
2008-01-20 13:54 ` [Bug middle-end/34884] " dominiq at lps dot ens dot fr
2008-01-20 13:54 ` pinskia at gcc dot gnu dot org
2008-01-20 15:17 ` zadeck at naturalbridge dot com
2008-01-20 15:22 ` dominiq at lps dot ens dot fr
2008-01-20 15:35 ` zadeck at naturalbridge dot com
2008-01-20 15:40 ` dominiq at lps dot ens dot fr
2008-01-20 16:07 ` zadeck at naturalbridge dot com
2008-01-20 16:29 ` dominiq at lps dot ens dot fr
2008-01-20 16:31 ` zadeck at naturalbridge dot com
2008-01-20 16:35 ` [Bug fortran/34884] " hjl dot tools at gmail dot com
2008-01-20 19:39 ` zadeck at naturalbridge dot com
2008-01-20 22:29 ` [Bug middle-end/34884] " pinskia at gcc dot gnu dot org
2008-01-21  0:05 ` zadeck at naturalbridge dot com
2008-01-21  0:13 ` steven at gcc dot gnu dot org
2008-01-21  0:28 ` zadeck at naturalbridge dot com
2008-01-21  9:08 ` bonzini at gnu dot org
2008-01-21 13:23 ` zadeck at naturalbridge dot com
2008-01-21 13:42 ` bonzini at gnu dot org
2008-01-21 13:55 ` zadeck at naturalbridge dot com
2008-01-21 14:44 ` stevenb dot gcc at gmail dot com
2008-01-21 14:55 ` dominiq at lps dot ens dot fr
2008-01-21 14:55 ` steven at gcc dot gnu dot org
2008-01-21 15:15 ` bonzini at gnu dot org
2008-01-21 15:15 ` rguenth at gcc dot gnu dot org
2008-01-21 15:43 ` zadeck at naturalbridge dot com
2008-01-21 16:44 ` jsm28 at gcc dot gnu dot org
2008-01-22 13:50 ` zadeck at naturalbridge dot com
2008-01-22 14:04 ` zadeck at gcc dot gnu dot org [this message]
2008-01-22 14:13 ` zadeck at naturalbridge dot com
2008-01-22 14:47 ` zadeck at naturalbridge dot com

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=20080122135750.32647.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).