From: Jason Merrill <jason@redhat.com>
To: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR c++/50055: Location information for the throw() specification in a function may be incorrect
Date: Tue, 23 Aug 2011 15:39:00 -0000 [thread overview]
Message-ID: <4E53BF9A.6060407@redhat.com> (raw)
In-Reply-To: <CAAHN_R2AiK_uCtc-eSv899=EpCK7RtKTN66XtTgUb=Yni3Ut=Q@mail.gmail.com>
On 08/12/2011 03:18 PM, Siddhesh Poyarekar wrote:
> When the location for throw() exception specification is not the same
> as the function it is written against, it leads gcov to give incorrect
> results. See bug 50055 for details of the the same. The following
> patch makes sure that the exception specification block (nothrow or
> otherwise) is always associated with the function definition line
> number.
I'm applying this patch, thanks.
This patch is small enough not to need it, but for future contributions
please file a copyright assignment with the FSF. Send email to
assign@gnu.org for more information.
Jason
next prev parent reply other threads:[~2011-08-23 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 19:39 Siddhesh Poyarekar
2011-08-23 15:39 ` Jason Merrill [this message]
2011-08-23 15:43 ` Jakub Jelinek
2011-08-23 15:45 ` Siddhesh Poyarekar
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=4E53BF9A.6060407@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=siddhesh.poyarekar@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).