public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/16586] [3.3/3.4 Regression] -O3 -fno-gcse ICE verify_local_live_at_start flow.c:575 Date: Thu, 02 Dec 2004 07:11:00 -0000 [thread overview] Message-ID: <20041202071114.7676.qmail@sourceware.org> (raw) In-Reply-To: <20040716071005.16586.ned@bike-nomad.com> ------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-12-02 07:11 ------- This one is really tricky to fix: this is the classical case in which the return value register's liveness propagates backwards until an unrelated use/clobber of the register is encountered. This works more or less until the regrename pass, which locally renames the register in the latter def/use/clobber chain; so the return value register's liveness is not masked anymore and propagates back to the start of the basic block. But, after reload, register liveness information is not allowed to change at basic block boundaries so the compiler aborts on a sanity check. The easy workaround is to make sure that every code path in a function returning a value really returns a value. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16586
next prev parent reply other threads:[~2004-12-02 7:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-16 7:10 [Bug c/16586] New: gcc 3.3.3/3.3.4 " ned at bike-nomad dot com 2004-07-16 7:11 ` [Bug c/16586] " ned at bike-nomad dot com 2004-07-16 7:32 ` [Bug rtl-optimization/16586] [3.3 Regression] " pinskia at gcc dot gnu dot org 2004-07-16 11:04 ` gdr at gcc dot gnu dot org 2004-07-16 13:38 ` [Bug rtl-optimization/16586] [3.3/3.4 " bangerth at dealii dot org 2004-07-28 20:43 ` pinskia at gcc dot gnu dot org 2004-08-16 14:23 ` reichelt at gcc dot gnu dot org 2004-08-29 18:11 ` mmitchel at gcc dot gnu dot org 2004-08-29 18:25 ` mmitchel at gcc dot gnu dot org 2004-09-10 15:08 ` [Bug rtl-optimization/16586] [3.3 " reichelt at gcc dot gnu dot org 2004-09-10 19:18 ` rth at gcc dot gnu dot org 2004-09-16 14:12 ` [Bug rtl-optimization/16586] [3.3/3.4 " reichelt at gcc dot gnu dot org 2004-11-01 0:46 ` mmitchel at gcc dot gnu dot org 2004-12-02 7:11 ` ebotcazou at gcc dot gnu dot org [this message] 2004-12-05 9:39 ` ebotcazou at gcc dot gnu dot org 2005-05-19 17:48 ` mmitchel 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=20041202071114.7676.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).