public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/43085] Make profiledbootstrap fails with cc1plus catching SIGSEGV Date: Mon, 02 May 2011 14:19:00 -0000 [thread overview] Message-ID: <bug-43085-4-QTz5g1B1q5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43085-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43085 --- Comment #24 from Ulrich Weigand <uweigand at gcc dot gnu.org> 2011-05-02 14:06:52 UTC --- Author: uweigand Date: Mon May 2 14:06:48 2011 New Revision: 173252 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173252 Log: 2011-05-02 Ulrich Weigand <ulrich.weigand@linaro.org> PR middle-end/43085 Backport from mainline: 2010-04-29 Bernd Schmidt <bernds@codesourcery.com> From Dominique d'Humieres <dominiq@lps.ens.fr> PR bootstrap/43858 * ifcvt.c (dead_or_predicable): Use df_simulate_find_defs to compute test_set. 2010-04-26 Bernd Schmidt <bernds@codesourcery.com> * df-problems.c (df_simulate_initialize_forwards): Set, don't clear, bits for artificial defs at the top of the block. * fwprop.c (single_def_use_enter_block): Don't call it. 2010-04-22 Bernd Schmidt <bernds@codesourcery.com> * ifcvt.c (dead_or_predicable): Use df_simulate_find_defs and df_simulate_find_noclobber_defs as appropriate. Keep track of an extra set merge_set_noclobber, and use it to relax the final test slightly. * df.h (df_simulate_find_noclobber_defs): Declare. * df-problems.c (df_simulate_find_defs): Don't ignore partial or conditional defs. (df_simulate_find_noclobber_defs): New function. Modified: branches/gcc-4_5-branch/gcc/ChangeLog branches/gcc-4_5-branch/gcc/df-problems.c branches/gcc-4_5-branch/gcc/df.h branches/gcc-4_5-branch/gcc/fwprop.c branches/gcc-4_5-branch/gcc/ifcvt.c
prev parent reply other threads:[~2011-05-02 14:19 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43085-4@http.gcc.gnu.org/bugzilla/> 2010-10-11 17:46 ` [Bug c++/43085] " jamborm at gcc dot gnu.org 2010-10-12 12:25 ` aanisimov at inbox dot ru 2010-10-12 12:28 ` aanisimov at inbox dot ru 2010-10-13 14:31 ` fierevere at ya dot ru 2010-10-13 14:38 ` jamborm at gcc dot gnu.org 2010-10-13 15:11 ` fierevere at ya dot ru 2010-10-13 17:48 ` aanisimov at inbox dot ru 2010-12-16 11:15 ` jamborm at gcc dot gnu.org 2010-12-21 14:35 ` jamborm at gcc dot gnu.org 2010-12-21 14:44 ` onur at pardus dot org.tr 2010-12-21 17:11 ` onur at pardus dot org.tr 2011-02-28 9:56 ` onur at pardus dot org.tr 2011-02-28 10:09 ` onur at pardus dot org.tr 2011-04-13 7:24 ` fierevere at ya dot ru 2011-04-13 7:24 ` michael.hope at linaro dot org 2011-04-27 16:19 ` [Bug middle-end/43085] " uweigand at gcc dot gnu.org 2011-04-27 16:29 ` uweigand at gcc dot gnu.org 2011-05-02 14:18 ` uweigand at gcc dot gnu.org 2011-05-02 14:19 ` uweigand 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-43085-4-QTz5g1B1q5@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).