From: Jason Merrill <jason@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: RFA PATCH to get_narrower for c++/48106 (ICE with scoped enum)
Date: Mon, 23 May 2011 16:17:00 -0000 [thread overview]
Message-ID: <4DDA7F67.2030003@redhat.com> (raw)
In-Reply-To: <BANLkTinzwJPMT5Hbg7Zxr56YmKOk6gDskQ@mail.gmail.com>
On 05/23/2011 11:01 AM, Richard Guenther wrote:
> Ok. Though I wonder where you enter folding before you check semantic
> validity.
The problem is in c-common:shorten_binary_op, which uses get_narrower
and then calls common_type on the types of the results. There is no
common type between a scoped enum and char, so common_type returns
NULL_TREE, so we get a SEGV in c_common_signed_or_unsigned_type.
Do you think I should change shorten_binary_op instead?
Jason
next prev parent reply other threads:[~2011-05-23 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 15:04 Jason Merrill
2011-05-23 15:46 ` Richard Guenther
2011-05-23 16:17 ` Jason Merrill [this message]
2011-05-23 16:25 ` Richard Guenther
2011-05-24 5:33 ` Jason Merrill
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=4DDA7F67.2030003@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).