public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/53590] compiler fails to generate SIMD instruction for FP division Date: Fri, 15 Jun 2012 09:22:00 -0000 [thread overview] Message-ID: <bug-53590-4-JSyLoVgDvV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53590-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53590 --- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-06-15 09:22:04 UTC --- Author: ebotcazou Date: Fri Jun 15 09:22:00 2012 New Revision: 188651 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188651 Log: PR middle-end/53590 * common.opt (-fdelete-dead-exceptions): New switch. * doc/invoke.texi (Code Gen Options): Document it. * cse.c (count_reg_usage) <CALL_INSN>: Use !insn_nothrow_p in lieu of insn_could_throw_p predicate. Do not skip an insn that could throw if dead exceptions can be deleted. (insn_live_p): Likewise, do not return true in that case. * dce.c (can_alter_cfg): New flag. (deletable_insn_p): Do not return false for an insn that can throw if the CFG can be altered and dead exceptions can be deleted. (init_dce): Set can_alter_cfg to false for fast DCE, true otherwise. * dse.c (scan_insn): Use !insn_nothrow_p in lieu of insn_could_throw_ predicate. Do not preserve an insn that could throw if dead exceptions can be deleted. * function.h (struct function): Add can_delete_dead_exceptions flag. * function.c (allocate_struct_function): Set it. * lto-streamer-in.c (input_struct_function_base): Stream it. * lto-streamer-out.c (input_struct_function_base): Likewise. * tree-ssa-dce.c (mark_stmt_if_obviously_necessary): Do not mark a statement that could throw as necessary if dead exceptions can be deleted. ada/ * gcc-interface/misc.c (gnat_init_options_struct): Set opts->x_flag_delete_dead_exceptions to 1. Modified: trunk/gcc/ChangeLog trunk/gcc/ada/ChangeLog trunk/gcc/ada/gcc-interface/misc.c trunk/gcc/common.opt trunk/gcc/cse.c trunk/gcc/dce.c trunk/gcc/doc/invoke.texi trunk/gcc/dse.c trunk/gcc/function.c trunk/gcc/function.h trunk/gcc/lto-streamer-in.c trunk/gcc/lto-streamer-out.c trunk/gcc/tree-ssa-dce.c
next prev parent reply other threads:[~2012-06-15 9:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-06 13:14 [Bug ada/53590] New: new compiler generates both SISD and SIMD instructions for parallel operations of a "pure" function bauhaus at futureapps dot de 2012-06-06 13:29 ` [Bug ada/53590] " bauhaus at futureapps dot de 2012-06-10 8:42 ` ebotcazou at gcc dot gnu.org 2012-06-11 9:53 ` rguenth at gcc dot gnu.org 2012-06-11 10:09 ` georggcc at googlemail dot com 2012-06-11 10:31 ` georggcc at googlemail dot com 2012-06-11 10:39 ` [Bug ada/53590] compiler fails to generate SIMD instruction for FP division ebotcazou at gcc dot gnu.org 2012-06-11 10:59 ` georggcc at googlemail dot com 2012-06-12 16:54 ` ebotcazou at gcc dot gnu.org 2012-06-13 17:12 ` [Bug middle-end/53590] " georggcc at googlemail dot com 2012-06-15 9:22 ` ebotcazou at gcc dot gnu.org [this message] 2012-06-15 10:00 ` ebotcazou at gcc dot gnu.org 2012-06-15 14:54 ` georggcc at googlemail dot com 2012-06-16 11:06 ` ebotcazou at gcc dot gnu.org 2014-07-10 10:39 ` ebotcazou at gcc dot gnu.org 2014-07-10 10:41 ` ebotcazou 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-53590-4-JSyLoVgDvV@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).