public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28572] Misaligned accesses in test-memcpy and test-mempcpy on hppa Date: Thu, 11 Nov 2021 20:05:54 +0000 [thread overview] Message-ID: <bug-28572-131-r37Ltp59JW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28572-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28572 --- Comment #13 from dave.anglin at bell dot net --- On 2021-11-11 2:52 p.m., goldstein.w.n at gmail dot com wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=28572 > > --- Comment #9 from Noah Goldstein <goldstein.w.n at gmail dot com> --- > (In reply to H.J. Lu from comment #8) >> memcpy should work on unaligned addresses. Also we need to increase >> TIMEOUT for memcpy. > It does "work" still. But if it takes 400+ minutes its not really a useful > test. That only happens when the unaligned accesses fault. What's wrong with marking the src and dst types as unaligned pointers (i.e., alignment of 1)? It's easy to modify the typedef in the patch to only use alignment 1 on hppa and other strict alignment architectures. > > I think these tests are important for x86 but if the burden on other targets > is too high it doesn't seem reasonable to have them in `string/` I agree. HJL already bumped timeout. How much impact does patch have on x86? commit a6a9c1a36b48f304c8a2138c147d88a448161366 Author: H.J. Lu <hjl.tools@gmail.com> Date: Sun Nov 7 06:41:16 2021 -0800 test-memcpy.c: Double TIMEOUT to (8 * 60) commit d585ba47fcda99fdf228e3e45a01b11a15efbc5a Author: Noah Goldstein <goldstein.w.n@gmail.com> Date: Mon Nov 1 00:49:48 2021 -0500 string: Make tests birdirectional test-memcpy.c This commit updates the memcpy tests to test both dst > src and dst < src. This is because there is logic in the code based on the Signed-off-by: Noah Goldstein <goldstein.w.n@gmail.com> Reviewed-by: H.J. Lu <hjl.tools@gmail.com> significantly increased the number of tests. On Intel Core i7-1165G7, test-memcpy takes 120 seconds to run when machine is idle. Double TIMEOUT to (8 * 60) for test-memcpy to avoid timeout when machine is under heavy load. Dave -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-11 20:05 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-09 17:32 [Bug libc/28572] New: " danglin at gcc dot gnu.org 2021-11-09 17:42 ` [Bug libc/28572] " adhemerval.zanella at linaro dot org 2021-11-09 20:56 ` dave.anglin at bell dot net 2021-11-11 17:02 ` danglin at gcc dot gnu.org 2021-11-11 17:17 ` danglin at gcc dot gnu.org 2021-11-11 17:25 ` danglin at gcc dot gnu.org 2021-11-11 17:39 ` goldstein.w.n at gmail dot com 2021-11-11 17:53 ` dave.anglin at bell dot net 2021-11-11 18:22 ` goldstein.w.n at gmail dot com 2021-11-11 18:27 ` goldstein.w.n at gmail dot com 2021-11-11 19:50 ` hjl.tools at gmail dot com 2021-11-11 19:52 ` goldstein.w.n at gmail dot com 2021-11-11 20:03 ` hjl.tools at gmail dot com 2021-11-11 20:04 ` goldstein.w.n at gmail dot com 2021-11-11 20:05 ` adhemerval.zanella at linaro dot org 2021-11-11 20:05 ` dave.anglin at bell dot net [this message] 2021-11-11 20:24 ` dave.anglin at bell dot net 2021-11-11 20:30 ` goldstein.w.n at gmail dot com 2021-11-11 20:31 ` goldstein.w.n at gmail dot com 2021-11-12 14:51 ` danglin at gcc dot gnu.org 2021-12-08 4:21 ` goldstein.w.n at gmail dot com 2021-12-08 14:11 ` dave.anglin at bell dot net 2022-01-05 13:39 ` hjl.tools at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-28572-131-r37Ltp59JW@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).