public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Jay Foad <jay.foad@gmail.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
	       "Cc: David Malcolm" <dmalcolm@redhat.com>,
	       Jeffrey Law <law@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	       Richard Biener <richard.guenther@gmail.com>,
	       Dodji Seketeli <dodji@redhat.com>
Subject: Re: Fwd: libcpp/C FE source range patch committed (r230331).
Date: Tue, 24 Nov 2015 11:55:00 -0000	[thread overview]
Message-ID: <20151124115355.GS21807@redhat.com> (raw)
In-Reply-To: <CANd1uZ=wRf7emgmApBWE95PNToifKZskVczXiQRcsZJTjbOi7w@mail.gmail.com>

On Tue, Nov 24, 2015 at 11:50:21AM +0000, Jay Foad wrote:
> I see now that it's already reported as PR c/68473.

Ooops, sorry, I knew about that one, but thought that's a different problem.

	Marek

      reply	other threads:[~2015-11-24 11:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14 14:50 David Edelsohn
2015-11-15  4:32 ` David Malcolm
2015-11-16 20:50   ` [PATCH] Fix uninitialized src_range within c_expr (Re: libcpp/C FE source range patch committed (r230331)) David Malcolm
2015-11-16 21:34     ` Bernd Schmidt
2015-11-17 15:13       ` David Malcolm
2015-11-17 15:24         ` Bernd Schmidt
2015-11-17 20:12           ` David Malcolm
2015-11-21 18:58             ` David Edelsohn
2015-11-21 20:07               ` David Malcolm
2015-11-21 22:03                 ` David Edelsohn
     [not found] ` <CANd1uZkKmxqX_6y0M6dxgfpdf83HuXX9+gRBiqzYECqon54NrQ@mail.gmail.com>
2015-11-24 11:27   ` Fwd: libcpp/C FE source range patch committed (r230331) Jay Foad
2015-11-24 11:37     ` Marek Polacek
2015-11-24 11:54       ` Jay Foad
2015-11-24 11:55         ` Marek Polacek [this message]

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=20151124115355.GS21807@redhat.com \
    --to=polacek@redhat.com \
    --cc=dje.gcc@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=dodji@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jay.foad@gmail.com \
    --cc=law@redhat.com \
    --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).