From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9EAA6235C00 for ; Mon, 13 Jan 2025 11:16:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736766990; cv=none; b=mFUHR1CGLULuhh3N1IZKQuYE/YCM0vVT34a0gx9SZQubqVkdp+cn1gChDi5/pc6E5/LRp6Fger9QodX3NUtMjFX2YYn5MbFVqE8z5L9AWA5J/B+0c7QOQCgdCWMCXkqi6/p2TpEehbM8yV3FB9HP+CW8wnIGFVGhAlU6DN1lpLg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736766990; c=relaxed/simple; bh=02ICPJhuuWi3eHu0xuSsYX+04EPMzhe4Q8gL4tVGRHE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Dig2Rv6w4bp9UBI7ibBXJHMei1tV2mvlXdn67UC6xMXLOOH/Q676Ix00j4qIQchtFcGhuZ2l6zHTprCJdss5hSafo3Tw370WOoPVIA9KGi7QWkZd9+oLLUNCyulkjKaX9RRkWkgJvnAN0EIZvmkAb1F8InEynyllO8ONao1h97I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=hLzSEUzi; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="hLzSEUzi" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=Bq5K2gtd0CG5cw01T53Qmmcvxc0zFDUsb0flnn7zWgY=; b=hLzSEUziY+NNSDMHCZQxOWd89y hwrqmPuKiRdKMLVqMdHhuD1qAV0z4alnaBXpGQQrDNmAbcI5X3Nl+rVQtfjxnzjiedWCb0HOOLh0O oMd4YWnnPOW3bb2KxGtUCeYrek9sleqV9C4rbmKtPCUv4FJQKl2ylCligRb8eX29GQ8FhLmmX2klK R89aEl1qJI4azKh38TTfxlIm90mmPYBWaenqUWcwYFMx4mgFgaNRb+INsMNMcOWPeK4ALV2h+/tdr 2j1xCDHKMFcuQybtTnIjv3daPrxh/P+ZcS+c4/H5aewFz2wrcaWN5LWzf+ZFqKDZg6QgpN7Rnx52e wlK1M+5A==; Received: from 77-249-17-89.cable.dynamic.v4.ziggo.nl ([77.249.17.89] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.98 #2 (Red Hat Linux)) id 1tXIQi-00000000aXP-2mIP; Mon, 13 Jan 2025 11:16:25 +0000 Received: by noisy.programming.kicks-ass.net (Postfix, from userid 1000) id 4652730057A; Mon, 13 Jan 2025 12:16:24 +0100 (CET) Date: Mon, 13 Jan 2025 12:16:24 +0100 From: Peter Zijlstra To: "Paul E. McKenney" Cc: linux-toolchains@vger.kernel.org Subject: Re: Do we care if C compilers start allowing "." on pointers? Message-ID: <20250113111624.GG5388@noisy.programming.kicks-ass.net> References: <6c55adc5-52f9-45e2-aa20-ef344c9dd1ea@paulmck-laptop> Precedence: bulk X-Mailing-List: linux-toolchains@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6c55adc5-52f9-45e2-aa20-ef344c9dd1ea@paulmck-laptop> On Fri, Jan 10, 2025 at 07:02:14AM -0800, Paul E. McKenney wrote: > Hello! > > Currently, given a pointer "p", C allows p->a but not p.a. There is a > proposal from C++ [1] that is being considered for C. > > Do we care? After buying a new WTF'o'meter -- reading about this proposal definitely shattered the old one -- I'm with everybody else so far, this will not make C better, and if it ever were to pass, we should ensure the kernel does not use it.