From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound-ss-761.bluehost.com (outbound-ss-761.bluehost.com [74.220.211.250]) by sourceware.org (Postfix) with ESMTPS id 339E83858C50 for ; Mon, 2 May 2022 17:04:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 339E83858C50 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw12.mail.unifiedlayer.com (unknown [10.0.90.127]) by progateway8.mail.pro1.eigbox.com (Postfix) with ESMTP id 479A8100421B8 for ; Mon, 2 May 2022 17:04:19 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id lZT8nMbzkb2WGlZT8ndvFB; Mon, 02 May 2022 17:04:19 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=SqtVVNC0 c=1 sm=1 tr=0 ts=62700f13 a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=oZkIemNP1mAA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=p_m6AggRm2iVPSyezVcA:9 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=H9gTA2TKGrM+/WBE9V8eGO6Bl2Q2UqoPpRmY4d89i5I=; b=ZzPTePLy95id1Oct+XChQ0MsSr TWOg+AQTjJjq/SCTUZojjYGt6K7h9/7KgWtI3A4Xrm7expLJ87W30e1rLQI+duWBprdEGECdYQj6R ykDPCg7wpCZ9eoLWyUWBQCNof; Received: from 71-211-158-194.hlrn.qwest.net ([71.211.158.194]:34652 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nlZT8-0038Ug-CH; Mon, 02 May 2022 11:04:18 -0600 From: Tom Tromey To: Pedro Alves Cc: Tom Tromey , Zied Guermazi , gdb-patches@sourceware.org Subject: Re: [PATCH 1/1] get page size using sysconf (_SC_PAGESIZE) instead of PAGE_SIZE References: <20220430121623.42196-1-zied.guermazi@trande.de> <20220430121623.42196-2-zied.guermazi@trande.de> <87sfprkhy6.fsf@tromey.com> <6e8148d5-bba1-86e2-313c-b9e99042874c@palves.net> X-Attribution: Tom Date: Mon, 02 May 2022 11:04:17 -0600 In-Reply-To: <6e8148d5-bba1-86e2-313c-b9e99042874c@palves.net> (Pedro Alves's message of "Mon, 2 May 2022 17:50:41 +0100") Message-ID: <87sfpr50j2.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 71.211.158.194 X-Source-L: No X-Exim-ID: 1nlZT8-0038Ug-CH X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 71-211-158-194.hlrn.qwest.net (prentzel) [71.211.158.194]:34652 X-Source-Auth: tom+tromey.com X-Email-Count: 3 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3023.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2022 17:04:21 -0000 Pedro> Please don't merge it yet. Andreas' question is quite pertinent Pedro> -- this file in only built on x86 hosts. The premise of the Pedro> patch doesn't seems strange offhand. Is the Aarch64 port going Pedro> to start using linux-btrace.c? That isn't clear. Based on the thread I assumed it was in preparation for such a merge. I suppose I don't really know for sure, but on the other hand it also seemed like this wasn't harmful. Tom