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.129.124]) by sourceware.org (Postfix) with ESMTPS id A3B5A3858C33 for ; Mon, 15 Jan 2024 13:40:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A3B5A3858C33 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org A3B5A3858C33 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1705326048; cv=none; b=Yt8T3k+DvBhfy0xqxhx4lenIdt4NalazAR+Pmvzk6NhRZ20tqrpXmN/GHSjDwE27DyIaFLi8bfcZb4m4FXuMUn8+Tt+ruLrlvt6He0wahZPeq6gI/3Hr5L1SKN3TNn+WanGYIqiOC6kylNwAgneRyF4OV+izvmb7J4ShFKuyD4w= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1705326048; c=relaxed/simple; bh=43w7GMMl4uGRpIUS+qLPfNmyOiU4ugRqxqAXus4ws3E=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=WBz3tIHVlf7hJb+RM9LKJhzKHMmO586MY0sENJXOyjjAHXfjy+blDWyMXMsQS5HdQDtpGCYq1ULau4hgkDb7KfPWmDDSUBs/Ap83fI0gS9+NLWymHWfGRwP9/crn9OvIlr4N8QgR3MLnfa8obfHKOPgxnrVoy0aBWeMkfcKBM5Q= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1705326047; 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=HFKFUNzNcoMKKQMhr0juKYhRoLYz1eWwFnrpLgPiCcg=; b=PQp7O4MBZuEahzFjatYQDstUx/IAK4mcyBBod69u7NUt5puTClawrcL2kucZhODd2xxtAd aylxTlh1D7dybnyale2t6KWLuP/dKYlikqSmjihN5h1XV2qgHcWPqFRVasmhk1d3mm9QJl fjaLyGRmwq5gGpzpzumxXlVDD8JqvTk= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-679-r7bxv3zCMhONeCS6uPlsJg-1; Mon, 15 Jan 2024 08:40:41 -0500 X-MC-Unique: r7bxv3zCMhONeCS6uPlsJg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 91B3B811E86; Mon, 15 Jan 2024 13:40:41 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.140]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5CB5BC15E6A; Mon, 15 Jan 2024 13:40:40 +0000 (UTC) From: Florian Weimer To: Antonios Salios via Libc-help Cc: Antonios Salios , Jan Henrik Weinstock , Lukas =?utf-8?Q?J=C3=BCnger?= Subject: Re: 64 bit time_t on riscv32 References: Date: Mon, 15 Jan 2024 14:40:38 +0100 In-Reply-To: (Antonios Salios via Libc-help's message of "Mon, 15 Jan 2024 13:52:52 +0100") Message-ID: <877cka7m09.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.8 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,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE 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: * Antonios Salios via Libc-help: > According to a kernel maintainer, the __USE_TIME_BITS64 macro should be > set on architectures that use 64-bit time [2], otherwise the kernel > headers will not be able to pick the correct definition. __USE_TIME_BITS64 is an internal glibc macro. It is not used on architectures which have a 64-bit time_t by default. Surely the UAPI headers know which time size the architecture uses in the kernel interface, and can be written arcordingly? Thanks, Florian