From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id A4E333858D39; Thu, 29 Jun 2023 15:18:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A4E333858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1688051905;
	bh=UN7jwGo18vTv2eMx+ncO2H43yR4FPJfVSpFfSuvK/+E=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=MxdX+2Uqn3HVOMlKM8SmSdPe/2Z0lnSNsPRhaI6mXxeyE/V8YJX8j250KILHI9Dju
	 DNyedFj5ERxf0YQ8FjHeDaviKTur/+0aZNGsx+vT4tsvqb00tpMN/pBxwBDnsZQYed
	 V/fCcvgQ5vbC0BMXa5tIQ0MynZgmFuYGS3TSg14c=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.39
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ppluzhnikov at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30516-131-bAHDwMxVGl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30516-131@http.sourceware.org/bugzilla/>
References: <bug-30516-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30516

--- 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?=20

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 (compar=
ed
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), b=
ut
this will likely become a problem for implementation.

This is already a problem when using C++ modules with Clang.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=