From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24917 invoked by alias); 8 Dec 2017 10:04:41 -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 24161 invoked by uid 89); 8 Dec 2017 10:04:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-11.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*RU:209.85.128.194, Hx-spam-relays-external:209.85.128.194, H*r:sk:static., HERE X-HELO: mail-wr0-f194.google.com Received: from mail-wr0-f194.google.com (HELO mail-wr0-f194.google.com) (209.85.128.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 08 Dec 2017 10:04:38 +0000 Received: by mail-wr0-f194.google.com with SMTP id l22so10269271wrc.11 for ; Fri, 08 Dec 2017 02:04:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id; bh=9stIARIPvrHLH571scKXfPcy/dMKJ5UJCGKNuqDW2WI=; b=Op5yTnFOWS/qRGNajekQU6UwldVDCmvdZqOENhrjKnUUSN+Wz8uDZwy4AnKVDmYpYe cM+7Qbm0bT+ml1JGr/voRZpTE72iXDSTGjETrtE5tZnpzSWfvOtLE7lI56NFvYSqse9b WXirgEGH6w5XaGNiYW8MYS/HoiX8m3XJJJ1sSQSeu0I+66UYLfudSMGCy0XF1zbRpDRc a8UirtGuoGwd1n6jM+61u+x4K/QUwA5pVepi538WJGZrOi4uVc56ItUVtM1aeh/+fvPg RW9gdtJxTow+ycO3svKteKYUWRWbzWZqnQoh6ighsB1uM/UdFPMZWcM7HcKSJxdv4DER 4jPw== X-Gm-Message-State: AJaThX6GfpvJ9nW7cMPTZ5tqpAkrji+MfdFvTw/d6ZmAyFDaVItFKZPo 0KdX7cN3yG1YAevm7urzKsR9bg== X-Google-Smtp-Source: AGs4zMZtn/wQsmZSsSJiYOHLmm3U856aecqoMbTonHcC9GqksbXYxz+xAFTh70UlU+V88GeOa4TGoA== X-Received: by 10.223.139.199 with SMTP id w7mr23056280wra.282.1512727476354; Fri, 08 Dec 2017 02:04:36 -0800 (PST) Received: from E107787-LIN.cambridge.arm.com (static.42.136.251.148.clients.your-server.de. [148.251.136.42]) by smtp.gmail.com with ESMTPSA id a22sm1194394wme.46.2017.12.08.02.04.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Dec 2017 02:04:35 -0800 (PST) From: Yao Qi X-Google-Original-From: Yao Qi To: gdb-patches@sourceware.org Subject: [PATCH 0/3 v3] [AArch64] Support tagged pointer Date: Fri, 08 Dec 2017 10:04:00 -0000 Message-Id: <1512727471-30745-1-git-send-email-yao.qi@linaro.org> X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00159.txt.bz2 ARMv8 supports tagged address, that is, the top one byte in address is ignored. It is always enabled on aarch64-linux. See https://www.kernel.org/doc/Documentation/arm64/tagged-pointers.txt Some parts of GDB related to address are updated in this patch series, - Memory access, like command 'x', - Setting hw breakpoint on some address, - Setting watchpoint on some address, Address tag is treated as non-significant bits of address, so this patch series add a new gdbarch significant_addr_bit, and use it in gdbarch to get rid of non-significant bits. This was the suggestion in the v2 review. (https://sourceware.org/ml/gdb-patches/2017-10/msg00792.html) When I test this patch series, and I find a regression in linespec. I posted the fix https://sourceware.org/ml/gdb-patches/2017-12/msg00158.html Without this fix, this series causes a regression. *** BLURB HERE *** Yao Qi (3): Clear non-significant bits of address on memory access Adjust breakpoint address by clearing non-significant bits Clear non-significant bits of address in watchpoint gdb/aarch64-linux-tdep.c | 2 + gdb/breakpoint.c | 22 ++--- gdb/gdbarch.c | 22 +++++ gdb/gdbarch.h | 8 ++ gdb/gdbarch.sh | 6 ++ gdb/target.c | 2 + gdb/testsuite/gdb.arch/aarch64-tagged-pointer.c | 57 ++++++++++++ gdb/testsuite/gdb.arch/aarch64-tagged-pointer.exp | 105 ++++++++++++++++++++++ gdb/utils.c | 17 ++++ gdb/utils.h | 3 + 10 files changed, 233 insertions(+), 11 deletions(-) create mode 100644 gdb/testsuite/gdb.arch/aarch64-tagged-pointer.c create mode 100644 gdb/testsuite/gdb.arch/aarch64-tagged-pointer.exp -- 1.9.1