public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis187 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/12082] [3.3/3.4 regression] Inappropriate unreachable code warnings
Date: Fri, 29 Aug 2003 00:09:00 -0000	[thread overview]
Message-ID: <20030829000917.4924.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030827203936.12082.augart@us.ibm.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


janis187 at us dot ibm dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jh at suse dot cz


------- Additional Comments From janis187 at us dot ibm dot com  2003-08-29 00:09 -------
The regression in PR 12082 was introduced or exposed by this patch:

--- gcc/gcc/ChangeLog ---

Don Feb 28 11:07:36 CET 2002  Jan Hubicka  <jh@suse.cz>

        * basic-block.h (BB_REACHABLE): Renumber.
        (BB_DIRTY, BB_NEW): New flags.
        (clear_bb_flags): Declare.
        (update_life_info_in_dirty_blocks): Declare.
        * cfg.c (clear_bb_flags): New function.
        * cfgrtl.c (create_basic_block_structure): Set flags to BB_NEW.
        * emit-rtl.c (add_insn_after, add_insn_before, remove_insn,
        reorder_insns, emit_insn_after): Mark block as dirty.
        * flow.c (update_life_info): Fix clearing of PROP_LOG_LINKS.
        (update_life_info_in_dirty_blocks): New function.
        * recog.c (apply_change_group): Dirtify block.

        * cse.c (cse_insn): Reorder emitting of jump insn to keep
        cfg consistent.
        * gcse.c (delete_null_pointer_checks): Likewise.

        * toplev.c (dump_file_index): Move cse2 after bp,
        add DFI_null
        (dump_file_info): Similary.
        (rest_of_compilation): Avoid most of CFG rebuilds;
        do first if converision after null pointer checks, do cse2
        after branch prediction; avoid full liveness rebuild after
        initializing subregs.
        * invoke.texi (-d options): Document -du, renumber.

        * cfgcleanup.c (bb_flags): Remove BB_UPDATE_LIFE.
        (notice_new_block): Do not set BB_UPDATE_LIFE.
        (try_forward_edges, merge_blocks_move_predecessor_nojumps,
         merge_blocks_move_successor_nojumps, merge_blocks,
         try_crossjump_to_edge): Likewise.
        (try_optimize_cfg): Likewise; use update_life_info_in_dirty_blocks.
        * cfgrtl.c (merge_blocks_nomove): Copy b's flags to a.
        * ifcvt.c (SET_UPDATE_LIFE, UPDATE_LIFE): Kill.
        (merge_of_block): Do not use life_data_ok.
        (find_if_case_1): Do not use SET_UPDATE_LIFE.
        (if_convert): Use BB_DIRTY mechanizm to update life.
        * lcm.c (optimize_mode_switching): Update
        update_life_info_in_dirty_blocks

The regression hunt took place on i686-pc-linux-gnu using Wolfgang's
small test case from comment #7 compiled with "-O3 -Wunreachable-code".


  parent reply	other threads:[~2003-08-29  0:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 20:39 [Bug optimization/12082] New: " augart at us dot ibm dot com
2003-08-27 20:41 ` [Bug optimization/12082] " augart at us dot ibm dot com
2003-08-27 20:42 ` augart at us dot ibm dot com
2003-08-27 21:57 ` bangerth at dealii dot org
2003-08-28 17:25 ` augart at us dot ibm dot com
2003-08-28 17:27 ` augart at us dot ibm dot com
2003-08-28 17:28 ` augart at us dot ibm dot com
2003-08-28 17:29 ` augart at us dot ibm dot com
2003-08-28 17:52 ` bangerth at dealii dot org
2003-08-28 17:53 ` [Bug optimization/12082] [3.3/3.4 regression] " bangerth at dealii dot org
2003-08-28 20:45 ` augart at us dot ibm dot com
2003-08-29  0:09 ` janis187 at us dot ibm dot com [this message]
2003-09-05  5:32 ` mmitchel at gcc dot gnu dot org
2003-09-06 21:26 ` cvs-commit at gcc dot gnu dot org
2003-09-06 21:50 ` cvs-commit at gcc dot gnu dot org
2003-09-07  3:21 ` pinskia 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=20030829000917.4924.qmail@sources.redhat.com \
    --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).