public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot bonzini at lu dot unisi dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23948] [4.1 Regression] internal compiler error: verify_stmts failed
Date: Wed, 21 Sep 2005 14:33:00 -0000	[thread overview]
Message-ID: <20050921143320.18198.qmail@sourceware.org> (raw)
In-Reply-To: <20050918131230.23948.harold@alum.mit.edu>


------- Additional Comments From paolo dot bonzini at lu dot unisi dot ch  2005-09-21 14:33 -------
Subject: Re:  [4.1 Regression] internal compiler
 error: verify_stmts failed

rguenth at gcc dot gnu dot org wrote:

>------- Additional Comments From rguenth at gcc dot gnu dot org  2005-09-21 14:18 -------
>We insert the reciprocal computation correctly after the call to 
>  double prrs = potentially_runnable_resource_share();
>but as this call may trap and is the last instruction in the basic block,
>inserting there is obviously bogous.
>
>We'd need to insert a new BB or need a way to insert on the EXIT_EDGE.  And
>make sure critical edges are split.
>  
>
No, I think we have to rethink the place where we insert the division.  
It needs to be closer to the divide (just before), not right after the 
definition.  When we have flag_trapping_math, this is quite hard to do 
(there may be even multiple places to insert the divide!).

I also did not understand why you had to fiddle with postdominators :-) 
to fix PR23309.  I have a prototype patch but it will probably be a 
while before I can sit, look if it really works, and test it properly.

Paolo


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23948


  parent reply	other threads:[~2005-09-21 14:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 13:12 [Bug c++/23948] New: " harold at alum dot mit dot edu
2005-09-18 13:16 ` [Bug c++/23948] " harold at alum dot mit dot edu
2005-09-18 15:30 ` harold at alum dot mit dot edu
2005-09-18 16:33 ` pinskia at gcc dot gnu dot org
2005-09-18 18:02 ` harold at alum dot mit dot edu
2005-09-18 18:06 ` pinskia at gcc dot gnu dot org
2005-09-18 18:10 ` pinskia at gcc dot gnu dot org
2005-09-18 18:17 ` [Bug tree-optimization/23948] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-18 18:54 ` pinskia at gcc dot gnu dot org
2005-09-20 21:28 ` janis187 at us dot ibm dot com
2005-09-21  8:13 ` bonzini at gcc dot gnu dot org
2005-09-21 14:19 ` rguenth at gcc dot gnu dot org
2005-09-21 14:33 ` paolo dot bonzini at lu dot unisi dot ch [this message]
2005-09-21 14:44 ` rguenth at gcc dot gnu dot org
2005-09-22  7:00 ` bonzini at gcc dot gnu dot org
2005-09-22  7:09 ` bonzini at gcc dot gnu dot org
2005-09-23  9:58 ` bonzini at gcc dot gnu dot org
2005-09-25 12:48 ` bonzini at gcc dot gnu dot org
     [not found] <bug-23948-11342@http.gcc.gnu.org/bugzilla/>
2005-10-15 17:26 ` steven at gcc dot gnu dot org
2005-10-15 17:27 ` steven at gcc dot gnu dot org
2005-10-15 17:49 ` pinskia at gcc dot gnu dot org
2005-10-31  5:48 ` mmitchel at gcc dot gnu dot org
2006-01-11 14:29 ` bonzini at gcc dot gnu dot org
2006-01-11 14:31 ` bonzini at gnu dot org
2006-01-23  1:26 ` pinskia 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=20050921143320.18198.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: link
Be 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).