public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107755] [10/11/12/13 Regression] ICE: in fold_convert_loc, at fold-const.c:2435, with -Wlogical-op, implicit user-defined conversion operator, template function, logical operator, and conditional operator
Date: Thu, 24 Nov 2022 17:43:02 +0000	[thread overview]
Message-ID: <bug-107755-4-Xusb6ki5vm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107755-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107755

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
One possible fix would be not to emit these warnings while
processing_template_decl, the warning goes too deep into the expressions and
even when the operands are neither type nor value dependent, if
processing_template_decl they are far from what the middle-end code can grok.
I wonder where IMPLICIT_CONV_EXPR gets lost, so the COND_EXPR with
boolean_type_node type has RECORD_TYPE operand.

  parent reply	other threads:[~2022-11-24 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:27 [Bug c++/107755] New: " pokechu022+gccbugzilla at gmail dot com
2022-11-19  1:37 ` [Bug c++/107755] " pokechu022+gccbugzilla at gmail dot com
2022-11-21  8:53 ` marxin at gcc dot gnu.org
2022-11-21 19:48 ` mpolacek at gcc dot gnu.org
2022-11-21 19:49 ` [Bug c++/107755] [10/11/12/13 Regression] " mpolacek at gcc dot gnu.org
2022-11-24 17:43 ` jakub at gcc dot gnu.org [this message]
2023-01-31 19:29 ` mpolacek at gcc dot gnu.org
2023-02-01 13:31 ` cvs-commit at gcc dot gnu.org
2023-02-01 13:43 ` cvs-commit at gcc dot gnu.org
2023-02-01 13:44 ` [Bug c++/107755] [10/11 " mpolacek at gcc dot gnu.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=bug-107755-4-Xusb6ki5vm@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: 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).