public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/16851] re_node_set_alloc should not return REG_ESPACE when size == 0 Date: Fri, 18 Apr 2014 14:56:00 -0000 [thread overview] Message-ID: <bug-16851-132-rk2vTbluIu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16851-132@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16851 --- Comment #3 from Paul Eggert <eggert at gnu dot org> --- (In reply to Nathan Kennedy from comment #2) > re_node_set_alloc's use of malloc is not portable in that it needlessly > relies on current glibc malloc behavior not specified in any C standard Sure, but this is glibc. Glibc is allowed to rely on its own behavior, even if that behavior is not specified in the C standard. > such as in the two downstream projects (gnulib and uClibc). It's not a bug in gnulib, because of its use of MALLOC_0_IS_NONNULL. If there's a uClibc bug, they can fix it there. At some point, we may unify gnulib regex and glibc regex, and and that point we'll deal with this, but in the meantime there is no bug here. The simplest fix for the uClibc issue may be to modify uClibc so that its malloc is compatible with glibc. Yes, the C standard alllows uClibc's gratuitous incompability with glibc, but it's not good software engineering practice. But this is not the correct forum to discuss uClibc issues. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-18 14:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-17 22:19 [Bug regex/16851] New: " nkennedy at grammatech dot com 2014-04-18 1:15 ` [Bug regex/16851] " eggert at gnu dot org 2014-04-18 14:37 ` nkennedy at grammatech dot com 2014-04-18 14:56 ` eggert at gnu dot org [this message] 2014-06-12 19:40 ` fweimer at redhat 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-16851-132-rk2vTbluIu@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@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).