From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58912 invoked by alias); 19 Oct 2017 13:25:22 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 58854 invoked by uid 89); 19 Oct 2017 13:25:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:401, H*r:sk:static. X-HELO: mail-wr0-f171.google.com Received: from mail-wr0-f171.google.com (HELO mail-wr0-f171.google.com) (209.85.128.171) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Oct 2017 13:25:21 +0000 Received: by mail-wr0-f171.google.com with SMTP id z99so5866783wrc.12 for ; Thu, 19 Oct 2017 06:25:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=MRvDiCtw517DxYhOOMkSyoIB3wiM78i8KMClhinx6bM=; b=uFm/WquRwgPf0GwDsOBu4F+fV50axYNzNUYejbZ09LnSrBryHqgF/c7p703hAZllBo 0ZYhsllWs3c0kd32z5mknkLX3NYkNpGH+3rQ/jqk/OX9HHtTGktfIvLTcwI1U9cK24Ky bDuFCsbPxAPaKo01zvVOjeaLuucm8OKq2d4/PMHoHQci29IW7ebplQIvA922DRasxl0D lAYvMLy1hdsTFJOyWHMRUxeE1AgudNM07piX0aAfVYmiim4keL6Sox6qZvwcLkA7swXu cGgmlWaGjz+Yl2h7bnfOfF3xXSobrqmleUdrjR1Kk1oS9qhoVgNa1cxGm4UT7XilOFg1 FOYw== X-Gm-Message-State: AMCzsaVN4ZOKYTlV2nEupmQRvRqRXCblgJtdYwvPfSYRL2jbnpGDY070 rCM3luITTMIVelI5vmhhGDFIqQ== X-Google-Smtp-Source: ABhQp+SjrfBsi+BFmFWvO0XaRcFjotB1LUKJQDlnJb/hCzz3AI3tlOYUmWg9SiteU97EsMR3gCIqrQ== X-Received: by 10.223.164.18 with SMTP id d18mr1787746wra.232.1508419518710; Thu, 19 Oct 2017 06:25:18 -0700 (PDT) Received: from E107787-LIN (static.42.136.251.148.clients.your-server.de. [148.251.136.42]) by smtp.gmail.com with ESMTPSA id a79sm993815wma.38.2017.10.19.06.25.17 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Thu, 19 Oct 2017 06:25:17 -0700 (PDT) From: Yao Qi To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] [AArch64 Linux] Get rid of top byte from tagged address References: <1508400527-20718-1-git-send-email-yao.qi@linaro.org> <583291c9-a0d8-05ad-bf5e-0288d8ddcd80@redhat.com> Date: Thu, 19 Oct 2017 13:25:00 -0000 In-Reply-To: <583291c9-a0d8-05ad-bf5e-0288d8ddcd80@redhat.com> (Pedro Alves's message of "Thu, 19 Oct 2017 12:21:25 +0100") Message-ID: <86d15juv5w.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-10/txt/msg00608.txt.bz2 Pedro Alves writes: > Something else that came to mind -- do we need to make GDB's > stack/code caches aware of this? I.e., for the case of > writing through a tagged address and reading via a non-tagged > address, and vice-versa. Yes, we need take care of cache in gdb. Let me figure it out. --=20 Yao (=E9=BD=90=E5=B0=A7)