From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH] xen/common: Uniformally use __ varients for attribute names Date: Fri, 12 Feb 2016 09:56:53 +0000 Message-ID: <56BDAC65.8010107@citrix.com> References: <1455220302-32685-1-git-send-email-andrew.cooper3@citrix.com> <56BDB0E202000078000D14E2@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56BDB0E202000078000D14E2@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tim Deegan , Ian Campbell , Xen-devel List-Id: xen-devel@lists.xenproject.org On 12/02/16 09:16, Jan Beulich wrote: >>>> On 11.02.16 at 20:51, wrote: >> Otherwise, debug code such as "void __attribute__((noreturn)) foobar()" fails >> to compile when the noreturn itself gets expanded, resulting in >> __attribute__((__attribute__((noreturn)))). > Well, why would the debugging code not use plain "noreturn" then, > instead of open coding its expansion? That notwithstanding the > patch is fine of course. Which one works depends on whether has been included. There are some translation units in Xen where this is not the case. ~Andrew