public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/17428] internal compiler error: in spill_failure, at reload1.c:1880 (-fspeculative-prefetching) Date: Mon, 14 Feb 2005 16:03:00 -0000 [thread overview] Message-ID: <20050214113806.18929.qmail@sourceware.org> (raw) In-Reply-To: <20040912034129.17428.opticcow@linux-militia.net> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-14 11:38 ------- Subject: Bug 17428 CVSROOT: /cvs/gcc Module name: gcc Changes by: rakdver@gcc.gnu.org 2005-02-14 11:37:53 Modified files: gcc : ChangeLog value-prof.c cfgrtl.c Log message: PR target/17428 * cfgrtl.c (safe_insert_insn_on_edge): Avoid extending life range of hard registers. * value-prof.c (insn_prefetch_values_to_profile): Only scan normal insns. * value-prof.c (rtl_find_values_to_profile): Do not look for values to profile in libcalls. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.7467&r2=2.7468 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/value-prof.c.diff?cvsroot=gcc&r1=1.16&r2=1.17 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cfgrtl.c.diff?cvsroot=gcc&r1=1.157&r2=1.158 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17428
next prev parent reply other threads:[~2005-02-14 11:38 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-12 3:41 [Bug c/17428] New: internal compiler error: in spill_failure, at reload1.c:1880 opticcow at linux-militia dot net 2004-09-12 3:45 ` [Bug c/17428] " opticcow at linux-militia dot net 2004-09-12 3:54 ` pinskia at gcc dot gnu dot org 2004-09-12 3:54 ` pinskia at gcc dot gnu dot org 2004-09-12 3:56 ` [Bug rtl-optimization/17428] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-09-14 2:13 ` [Bug target/17428] " reichelt at gcc dot gnu dot org 2004-09-14 2:32 ` pinskia at gcc dot gnu dot org 2004-09-14 21:09 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-09-21 11:49 ` rakdver at gcc dot gnu dot org 2004-09-21 12:59 ` [Bug rtl-optimization/17428] " pinskia at gcc dot gnu dot org 2004-09-21 20:38 ` rakdver at gcc dot gnu dot org 2004-09-25 23:32 ` opticcow at linux-militia dot net 2004-10-16 13:29 ` reichelt at gcc dot gnu dot org 2004-10-28 9:28 ` reichelt at gcc dot gnu dot org 2004-10-28 11:42 ` reichelt at gcc dot gnu dot org 2004-10-28 13:19 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-11-04 7:06 ` rakdver at gcc dot gnu dot org 2004-11-27 0:25 ` [Bug rtl-optimization/17428] internal compiler error: in spill_failure, at reload1.c:1880 (-fspeculative-prefetching) pinskia at gcc dot gnu dot org 2005-02-14 16:03 ` cvs-commit at gcc dot gnu dot org [this message] 2005-02-15 20:53 ` reichelt at gcc dot gnu dot org 2005-04-11 9:47 ` reichelt at gcc dot gnu dot org 2005-04-11 10:33 ` reichelt at gcc dot gnu dot org 2005-04-11 10:41 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2005-06-02 16:08 ` reichelt at gcc dot gnu dot org 2005-07-29 9:41 ` reichelt 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=20050214113806.18929.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: 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).