[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 'noreturn' warning in libcruft
From: |
John W. Eaton |
Subject: |
Re: 'noreturn' warning in libcruft |
Date: |
Tue, 7 Aug 2012 15:16:53 -0400 |
On 7-Aug-2012, Michael Goffioul wrote:
| Won't GCC_ATTR_NORETURN always be defined, to something relevant or the empty
| string (otherwise you'd get a compilation error)? In that case, the above
| change won't have the expected result.
Oops, right. Do we need a corresponding HAVE_GCC_ATTR_NORETURN macro?
jwe
- 'noreturn' warning in libcruft, Rik, 2012/08/07
- Re: 'noreturn' warning in libcruft, Michael Goffioul, 2012/08/07
- Re: 'noreturn' warning in libcruft, Michael Goffioul, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07
- Re: 'noreturn' warning in libcruft, Michael Goffioul, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07
- Re: 'noreturn' warning in libcruft, Rik, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07
- Re: 'noreturn' warning in libcruft, Rik, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/08
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07