From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266850AbUGLP64 (ORCPT ); Mon, 12 Jul 2004 11:58:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266883AbUGLP64 (ORCPT ); Mon, 12 Jul 2004 11:58:56 -0400 Received: from mail.enyo.de ([212.9.189.167]:20241 "EHLO mail.enyo.de") by vger.kernel.org with ESMTP id S266850AbUGLP6q (ORCPT ); Mon, 12 Jul 2004 11:58:46 -0400 To: hpa@zytor.com (H. Peter Anvin) Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] Use NULL instead of integer 0 in security/selinux/ References: <20040707122525.X1924@build.pdx.osdl.net> From: Florian Weimer Date: Mon, 12 Jul 2004 17:58:43 +0200 In-Reply-To: (H. Peter Anvin's message of "Sun, 11 Jul 2004 20:05:54 +0000 (UTC)") Message-ID: <87r7rhb4jw.fsf@deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * H. Peter Anvin: > Followup to: > By author: Geert Uytterhoeven > In newsgroup: linux.dev.kernel >> >> - `return f();' in a function returning void (where f() returns void as well) >> > > Considering this one a bug is daft in the extreme. > > Why? Because "return f();" is the only kind of tailcall syntax C has, Huh? If you remove the "return", it's still a valid tailcall syntax (at least from GCC's perspective).