public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ayzhao at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30516] New: realpath() implementation has a C++ ODR violation Date: Mon, 05 Jun 2023 21:56:05 +0000 [thread overview] Message-ID: <bug-30516-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30516 Bug ID: 30516 Summary: realpath() implementation has a C++ ODR violation Product: glibc Version: 2.39 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: ayzhao at google dot com CC: drepper.fsp at gmail dot com Target Milestone: --- In stdlib/bits/stdlib.h, realpath is implemented as an inline function whose definition changes depending on whether or not limits.h was included first before stdlib.h [0]. In C++, this leads to an ODR violation if, for example, one translation unit includes stdlib.h and another translation unit includes limit.h and stdlib.h. [0]: https://sourceware.org/git/?p=glibc.git;a=blob;f=stdlib/bits/stdlib.h;h=c6c0082ad5b5fe0a9714326051f19818dedd5e11;hb=HEAD#l44 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-06-05 21:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-05 21:56 ayzhao at google dot com [this message] 2023-06-06 7:54 ` [Bug libc/30516] " schwab@linux-m68k.org 2023-06-25 23:40 ` ppluzhnikov at google dot com 2023-06-26 17:41 ` sam at gentoo dot org 2023-06-29 13:24 ` adhemerval.zanella at linaro dot org 2023-06-29 15:18 ` ppluzhnikov at google 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-30516-131@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).