public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30516] realpath() implementation has a C++ ODR violation Date: Thu, 29 Jun 2023 15:18:24 +0000 [thread overview] Message-ID: <bug-30516-131-bAHDwMxVGl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30516-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30516 --- Comment #3 from Paul Pluzhnikov <ppluzhnikov at google dot com> --- (In reply to Adhemerval Zanella from comment #2) > Do you have an example where the realpath fortify is generating ODR > violation? C++ modules. This happens before any inlining / code generation: the compiler imports a (precompiled) header module foo.pcm generated from foo.h with only "#include <stdlib.h>" into another source which includes both <limits.h> and <stdlib.h>, and observes that the sequence of tokens is different in current TU (compared to the sequence that was observed when foo.pcm was generated) and raises an error. > for GCC GCC does not fully support C++ modules yet (https://gcc.gnu.org/onlinedocs/gcc-11.2.0/gcc/C_002b_002b-Modules.html), but this will likely become a problem for implementation. This is already a problem when using C++ modules with Clang. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-06-29 15:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-05 21:56 [Bug libc/30516] New: " ayzhao at google dot com 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 [this message]
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-bAHDwMxVGl@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).