From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id DFBD63858D35 for ; Thu, 3 Nov 2022 18:33:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DFBD63858D35 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1667500412; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=82gkFlNrv2Tiz7CCjJ7+MDgk+g3xYGbGrAs9h4Ioauc=; b=ggTGaYUtsaP9z6bd/FEKwmWmCqgWxy9MgsX7bF/YWZX3EfvupAu5InBzZxmiYOJOy8s6BJ pawylO9bJT9l0xkYKAOP9QQzq+r2lKbcoNfljxnEQTjvqLtypOfgBVDBx/3/WXVaJzUCIZ zlO4zUJmScQyiDubpxOrsjguABax0b8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-634-9l1b_sS-M8atYPEIrV5Glw-1; Thu, 03 Nov 2022 14:33:29 -0400 X-MC-Unique: 9l1b_sS-M8atYPEIrV5Glw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 196B6185A7AC; Thu, 3 Nov 2022 18:33:29 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.64]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2697D40CA410; Thu, 3 Nov 2022 18:33:16 +0000 (UTC) From: Florian Weimer To: Joseph Myers Cc: gcc@gcc.gnu.org Subject: Re: Local type inference with auto is in C2X References: <87zgd8fhn4.fsf@oldenburg.str.redhat.com> <3f573e-a863-e1e6-f5be-83a6d7d32da0@codesourcery.com> Date: Thu, 03 Nov 2022 19:33:15 +0100 In-Reply-To: <3f573e-a863-e1e6-f5be-83a6d7d32da0@codesourcery.com> (Joseph Myers's message of "Thu, 3 Nov 2022 18:04:31 +0000") Message-ID: <87wn8bevmc.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Joseph Myers: > On Thu, 3 Nov 2022, Florian Weimer via Gcc wrote: > >> My main worry is that both Clang and GCC still enable implicit ints by >> default. This means that auto variables have type int always, and that >> can subtly alter the meaning of programs. The only indication that this >> has happened in a code base is a warning that went away (!). I don't >> like that. > > My expectation is that the old use of auto as a storage class specifier is > actually very rare in C code, so this particular sub-case (auto with no > type specifier meaning implicit int) is even rarer and there isn't much > porting to be done for it (unlike for the rest of implicit int). Hmm, that's certainly a reassuring perspective. Maybe I'm worrying about nothing after all. Thanks, Florian