From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [170.10.129.74]) by sourceware.org (Postfix) with ESMTPS id 26CFA3856255 for ; Fri, 6 May 2022 09:14:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 26CFA3856255 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=1651828452; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=IwhNNjhB/VCr12UAm4tXLD+olMB5eDaDs9ka5/x/f6A=; b=dGhgS6jp8/8mqB1DSQ31eyqfzQQh4yCOGD13BWCRGiCw++OOb61MAPe3DMvIWuGM0q4jj8 vX/Dk0ybP7VbLemSn3uWmJy3naMg1O1dbmj3rj9rMdaMRiUyqKcTNrkacH6kt9Dei4S/5/ IariacFlIuttTJPpe5mWzZN6m2XkxVM= 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-595-5mcuPUs6MvSfl-i2-W_dfQ-1; Fri, 06 May 2022 05:14:11 -0400 X-MC-Unique: 5mcuPUs6MvSfl-i2-W_dfQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 56E0018019D2 for ; Fri, 6 May 2022 09:14:11 +0000 (UTC) Received: from calimero.vinschen.de (unknown [10.36.112.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 32168200D8D7 for ; Fri, 6 May 2022 09:14:11 +0000 (UTC) Received: by calimero.vinschen.de (Postfix, from userid 500) id F201BA80984; Fri, 6 May 2022 11:14:09 +0200 (CEST) Date: Fri, 6 May 2022 11:14:09 +0200 From: Corinna Vinschen To: newlib@sourceware.org Subject: Re: Issue: #include shall not cause intmax_t to be defined Message-ID: Reply-To: newlib@sourceware.org Mail-Followup-To: newlib@sourceware.org References: <9dbc482d-84fd-b3be-babc-e00040a56f5b@embedded-brains.de> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=vinschen@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: newlib@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Newlib mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2022 09:14:14 -0000 On May 5 19:15, Pavel M wrote: > > Is there actually a "MUST NOT" defined anywhere in the standards or was > this change unnecessary? > C11 specifies when header X includes header Y. > Examples: > 7.25 Type-generic math : > > The header includes the headers and > 7.26 Threads : > > The header includes the header > 7.8 Format conversion of integer types : > > The header includes the header > There are no more occurrences of "includes the header". These examples define a MUST, where exposure of certain other header file definitions are expected by including a single other header. None of them defines a MUST NOT, which means that certain types are not to be exposed when including a certain other header. But, either way, the situation should be cleared by Sebastians patch. Corinna