This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch c++]: Fix PR/64100 'A static assert using the the current class in a noexcept test leads to a segfault'

From: Jason Merrill <jason at redhat dot com>
To: Kai Tietz <ktietz70 at googlemail dot com>, Marek Polacek <polacek at redhat dot com>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 04 Dec 2014 15:45:43 -0500
Subject: Re: [patch c++]: Fix PR/64100 'A static assert using the the current class in a noexcept test leads to a segfault'
Authentication-results: sourceware.org; auth=none
References: <CAEwic4bNBQ3r4E-7MetUPykZ7sL1TMEZ3sqUfTOBMJvtyS8hWg at mail dot gmail dot com> <20141204154644 dot GE16332 at redhat dot com> <CAEwic4Y27BT=+Na+Brim3vR8qmLOt5aN1A1X_JQagh_3PiAc1w at mail dot gmail dot com>

On 12/04/2014 10:57 AM, Kai Tietz wrote:

Well, I spared that as this is an invalid code bug with a lot of
side-errors, which might change over time.

Every patch should have an associated testcase unless it's fixing anexisting test or writing a testcase is somehow not feasible. Many testsin the testsuite deal with invalid code bugs. :)


Jason

Follow-Ups:
- Re: [patch c++]: Fix PR/64100 'A static assert using the the current class in a noexcept test leads to a segfault'
  - From: Kai Tietz

References:
- [patch c++]: Fix PR/64100 'A static assert using the the current class in a noexcept test leads to a segfault'
  - From: Kai Tietz
- Re: [patch c++]: Fix PR/64100 'A static assert using the the current class in a noexcept test leads to a segfault'
  - From: Marek Polacek
- Re: [patch c++]: Fix PR/64100 'A static assert using the the current class in a noexcept test leads to a segfault'
  - From: Kai Tietz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]