From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1FDDB3858C39; Thu, 14 Mar 2024 11:14:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1FDDB3858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710414853; bh=eML8I81nYOar+IE7q3o+aVOXsnWknjN6zuiPbNkOKDI=; h=From:To:Subject:Date:From; b=fJ8+iFL1/ktn68uFVSxOab8EtD3ZvsDb/O/KQ+DZzjGOAFrnOe32kQxkTd+u+L6Ys a8CDkAv6usKxKd1QVoG8Yqgmiqmj+CQRiXVQENvRCNSF9uqHy3XNuILg1hG/pxv7RU Pvtds+Qz7Pag9x5xukWAmBW/cZ0M4HrJJmnEinVw= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31484] New: [gdb/testsuite] Add memcpy, memmove, memset watchpoint tests Date: Thu, 14 Mar 2024 11:14:12 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31484 Bug ID: 31484 Summary: [gdb/testsuite] Add memcpy, memmove, memset watchpoint tests Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- While discussing aarch64 watchpoints, the point was raised that it's not cl= ear what addr_trap the kernel will report when using the aarch64 mops feature o= ps ( CPYF*, CPY*, SET* and SETG*). For now, there doesn't seem to a an SOC out there supporting this (looking = at https://gpages.juszkiewicz.com.pl/arm-socs-table/arm-socs.html). Nevertheless, we can add test-cases that excercise memset/memcpy/memmove and set watchpoints. On a mops architecture, using those will active the optim= ized versions in glibc which will use the mops feature ops. Likewise, on other architecture optimized versions may be triggered which f= avor larger memory access operations, which are interesting for testing watchpoi= nt behaviour. --=20 You are receiving this mail because: You are on the CC list for the bug.=