public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 44625
Date: Mon, 05 Jul 2010 13:10:00 -0000	[thread overview]
Message-ID: <4C31D9C7.9000209@redhat.com> (raw)
In-Reply-To: <4C31C773.3050000@oracle.com>

On 07/05/2010 07:52 AM, Paolo Carlini wrote:
> I have this patchlet for another case where we use BASELINK_P on
> NULL_TREE. Tested x86_64-linux. I propose to apply it to mainline and
> 4_5-branch only and then close the PR: it's a regression, but just a P5
> ice-on-invalid.

Seems like we ought to catch this when we're creating the COMPONENT_REF, 
rather than when we're trying to substitute into it; we shouldn't create 
a COMPONENT_REF with a null operand 1.

Jason

  reply	other threads:[~2010-07-05 13:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 11:52 Paolo Carlini
2010-07-05 13:10 ` Jason Merrill [this message]
2010-07-05 13:13   ` Paolo Carlini
2010-07-05 20:47     ` [C++ Patch] PR 44625, v2 Paolo Carlini
2010-08-17 15:49       ` Jason Merrill
2011-06-23 11:56 [C++ Patch] PR 44625 Paolo Carlini
2011-06-23 15:17 ` Jason Merrill
2011-06-23 15:47   ` Paolo Carlini
2011-06-23 16:01     ` Jason Merrill
2011-06-23 16:06       ` Paolo Carlini
2011-06-23 16:06         ` Jason Merrill
2011-06-23 16:06           ` Jason Merrill
2011-06-23 16:13             ` Paolo Carlini
2011-06-23 16:19               ` Paolo Carlini
2011-06-23 16:53             ` Paolo Carlini
2011-06-23 16:54               ` Jason Merrill
2011-06-23 16:11           ` Paolo Carlini

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=4C31D9C7.9000209@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paolo.carlini@oracle.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).