public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "post+sourceware.org at ralfj dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/31055] Request: guarantee that memcpy(x, x, n) is well-defined Date: Fri, 24 Nov 2023 08:52:14 +0000 [thread overview] Message-ID: <bug-31055-131-B3TFQPsbFi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31055-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31055 --- Comment #8 from Ralf Jung <post+sourceware.org at ralfj dot de> --- Is there a URL where that documentation can be found? That could be useful to reference in the future. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-24 8:52 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-11 17:37 [Bug string/31055] New: " post+sourceware.org at ralfj dot de 2023-11-11 18:41 ` [Bug string/31055] " sam at gentoo dot org 2023-11-13 18:47 ` adhemerval.zanella at linaro dot org 2023-11-18 17:56 ` post+sourceware.org at ralfj dot de 2023-11-21 15:30 ` adhemerval.zanella at linaro dot org 2023-11-23 7:36 ` post+sourceware.org at ralfj dot de 2023-11-23 11:53 ` adhemerval.zanella at linaro dot org 2023-11-23 14:48 ` sam at gentoo dot org 2023-11-23 15:18 ` post+sourceware.org at ralfj dot de 2023-11-24 7:46 ` rguenth at gcc dot gnu.org 2023-11-24 8:52 ` post+sourceware.org at ralfj dot de [this message] 2023-11-24 9:37 ` rguenth at gcc dot gnu.org 2023-11-28 7:18 ` sam at gentoo dot org
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-31055-131-B3TFQPsbFi@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).