[PATCH] PR c++/50055: Location information for the throw() specification in a function may be incorrect
Jason Merrill
jason@redhat.com
Tue Aug 23 15:39:00 GMT 2011
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
More information about the Gcc-patches
mailing list