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 tree-optimization/50693] Loop optimization restricted by GOTOs Date: Sat, 05 Nov 2011 19:59:00 -0000 [thread overview] Message-ID: <bug-50693-4-Ik2lVfaNyW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50693-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50693 --- Comment #25 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-11-05 19:58:41 UTC --- Author: jakub Date: Sat Nov 5 19:58:37 2011 New Revision: 181014 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181014 Log: PR tree-optimization/50693 * tree-cfg.c (gimple_can_merge_blocks_p): Allow merging with non-forced user labels. (gimple_merge_blocks): Turn non-forced user labels into debug bind stmt with the label as first operand and reset value. (gimple_duplicate_bb): Don't duplicate label debug stmts. * dwarf2out.c (gen_label_die): Handle NOTE_INSN_DELETED_DEBUG_LABEL. * final.c (final_scan_insn): Likewise. (rest_of_clean_state): Don't dump NOTE_INSN_DELETED_DEBUG_LABEL. * var-tracking.c (debug_label_num): New variable. (delete_debug_insns): Don't delete DEBUG_INSNs for LABEL_DECLs, instead turn them into NOTE_INSN_DELETED_DEBUG_LABEL notes. * cfglayout.c (skip_insns_after_block, duplicate_insn_chain): Handle NOTE_INSN_DELETED_DEBUG_LABEL. (duplicate_insn_chain): Don't duplicate LABEL_DECL DEBUG_INSNs. * insn-notes.def (DELETED_DEBUG_LABEL): New note kind. * print-rtl.c (print_rtx): Handle NOTE_INSN_DELETED_DEBUG_LABEL. * gengtype.c (adjust_field_rtx_def): Likewise. * config/i386/i386.c (ix86_output_function_epilogue): For MachO clear CODE_LABEL_NUMBER of NOTE_INSN_DELETED_DEBUG_LABEL if their are at the end of function and nop hasn't been emitted. * config/rs6000/rs6000.c (rs6000_output_function_epilogue): Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/cfglayout.c trunk/gcc/config/i386/i386.c trunk/gcc/config/rs6000/rs6000.c trunk/gcc/dwarf2out.c trunk/gcc/final.c trunk/gcc/gengtype.c trunk/gcc/insn-notes.def trunk/gcc/print-rtl.c trunk/gcc/tree-cfg.c trunk/gcc/var-tracking.c
next prev parent reply other threads:[~2011-11-05 19:59 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-10 22:45 [Bug c/50693] New: Slightly different loop body leads to 5.5x slower performance alex.gaynor at gmail dot com 2011-10-10 22:52 ` [Bug c/50693] " alex.gaynor at gmail dot com 2011-10-10 22:54 ` [Bug tree-optimization/50693] Slightly different loop body leads not vectoring loop pinskia at gcc dot gnu.org 2011-10-10 22:55 ` pinskia at gcc dot gnu.org 2011-10-10 23:57 ` dje at gcc dot gnu.org 2011-10-11 0:04 ` dje at gcc dot gnu.org 2011-10-11 0:22 ` dje at gcc dot gnu.org 2011-10-11 0:23 ` pinskia at gcc dot gnu.org 2011-10-11 1:12 ` [Bug tree-optimization/50693] Loop optimization restricted by GOTOs dje at gcc dot gnu.org 2011-10-11 1:24 ` pinskia at gcc dot gnu.org 2011-10-11 1:35 ` dje at gcc dot gnu.org 2011-10-11 7:15 ` irar at il dot ibm.com 2011-10-11 14:07 ` dje at gcc dot gnu.org 2011-10-11 14:13 ` rguenth at gcc dot gnu.org 2011-10-11 14:15 ` paolo.carlini at oracle dot com 2011-10-11 14:35 ` rguenth at gcc dot gnu.org 2011-10-11 14:36 ` rguenth at gcc dot gnu.org 2011-10-11 14:40 ` dje at gcc dot gnu.org 2011-10-11 14:44 ` rguenth at gcc dot gnu.org 2011-10-11 14:46 ` rguenth at gcc dot gnu.org 2011-10-11 14:51 ` jakub at gcc dot gnu.org 2011-10-11 16:04 ` alex.gaynor at gmail dot com 2011-10-12 15:21 ` rguenth at gcc dot gnu.org 2011-10-25 4:48 ` aoliva at gcc dot gnu.org 2011-11-04 17:18 ` jakub at gcc dot gnu.org 2011-11-05 19:59 ` jakub at gcc dot gnu.org [this message] 2011-11-05 20:09 ` alex.gaynor at gmail dot com 2012-03-26 10:35 ` jakub 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-50693-4-Ik2lVfaNyW@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: linkBe 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).