Date: Sat, 01 Jun 2024 05:49:09 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 279443] LIBCPP assertions are enabled in optimized builds when -DNDEBUG is given to clang Message-ID: <bug-279443-29464-uxuTlV0hjV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279443-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-279443-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279443 --- Comment #13 from Paul Floyd <pjfloyd@wanadoo.fr> --- (In reply to Mark Millard from comment #9) (In reply to Mark Millard from comment #9) The original comment said > It should be possible to get an address of the end of the std::vector obj= ect, even though it doesn't point to an allocated byte. This is precisely the purpose of std::end() (or std::vector::end(), std::en= d() has the advantage that it will also work with raw arrays). > I kept to a fairly minimal > style change compared to &buf[cb] and what it means in C and > some parts of C++ for my test example, using notation showing > specific distinctions that other C++ notations could hide and > so be less clear.=20 As I see it you were using idiomatic C to show how to do the wrong thing ra= ther than using idiomatic C++ to do the right thing. It looks like Yuri is getting things sorted out. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279443-29464-uxuTlV0hjV>