public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: gcc-bugzilla@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug c++/24439] [3.4/4.0/4.1 Regression] ICE with  invert conditional containing throw
Date: Wed, 19 Oct 2005 20:55:00 -0000	[thread overview]
Message-ID: <930547d2e105f6db518d09f384accf76@physics.uc.edu> (raw)
In-Reply-To: <20051019205027.26068.qmail@sourceware.org>


On Oct 19, 2005, at 4:50 PM, mark at codesourcery dot com wrote:

>
>
> ------- Comment #7 from mark at codesourcery dot com  2005-10-19 20:50 
> -------
> Subject: Re:  [3.4/4.0/4.1 Regression] ICE with  invert conditional
>  containing throw
>
> rguenth at gcc dot gnu dot org wrote:
>> ------- Comment #6 from rguenth at gcc dot gnu dot org  2005-10-19 
>> 20:40 -------
>> Unfortunately we call into the middle-ends invert_truthvalue right in
>> cp/typeck.c:build_unary_op as we build the TRUTH_NOT_EXPR, so at the 
>> time we
>> reach the gimplifier we already crashed.
>
> In that case, I think we should fix the middle end to handle this case;
> it's not a very major change to the semantics of GIMPLE/GENERIC to
> handle this case.  (I'm assuming that aren't massive ripple effects
> throughout the middle-end...)

Mark did you look how long this bug as been here, it predates tree-ssa
by a year.  So I don't think we should change TRUTH_NOT_EXPR/COND_EXPR
semantics.  The C++ front-end needs just stop doing bad stuff like this.

-- Pinski


  reply	other threads:[~2005-10-19 20:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 23:01 [Bug c++/24439] New: " dannysmith at users dot sourceforge dot net
2005-10-18 23:07 ` [Bug c++/24439] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-19  9:45 ` rguenth at gcc dot gnu dot org
2005-10-19  9:53 ` rguenth at gcc dot gnu dot org
2005-10-19 10:06 ` rguenth at gcc dot gnu dot org
2005-10-19 20:11 ` mmitchel at gcc dot gnu dot org
2005-10-19 20:40 ` rguenth at gcc dot gnu dot org
2005-10-19 20:50 ` mark at codesourcery dot com
2005-10-19 20:55   ` Andrew Pinski [this message]
2005-10-19 20:55 ` pinskia at physics dot uc dot edu
2005-10-19 20:58 ` mark at codesourcery dot com
2005-10-19 21:51 ` rguenth at gcc dot gnu dot org
2005-10-19 22:14 ` mark at codesourcery dot com
2005-10-20 15:19 ` cvs-commit at gcc dot gnu dot org
2005-10-20 15:45 ` [Bug c++/24439] [3.4/4.0 " rguenth at gcc dot gnu dot org
2005-11-17 11:24 ` [Bug c++/24439] " 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=930547d2e105f6db518d09f384accf76@physics.uc.edu \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).