public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108374] New: [12/13 Regression] unexpected -Wstringop-overflow when using std::atomic and std::shared_ptr Date: Wed, 11 Jan 2023 18:18:04 +0000 [thread overview] Message-ID: <bug-108374-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108374 Bug ID: 108374 Summary: [12/13 Regression] unexpected -Wstringop-overflow when using std::atomic and std::shared_ptr Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: romain.geissler at amadeus dot com Target Milestone: --- Hi, The following snippet produces an unexpected -Wstringop-overflow with gcc 12 and current trunk: #include <atomic> #include <memory> struct A: public std::enable_shared_from_this<A> { std::atomic<size_t> _attr; }; void f(std::shared_ptr<A> pointer) { std::weak_ptr<A> weakPointer(pointer); [[maybe_unused]] const unsigned int aAttr = weakPointer.lock()->_attr; } Compiler Explorer output: In file included from /opt/compiler-explorer/gcc-trunk-20230111/include/c++/13.0.0/atomic:41, from <source>:1: In member function 'std::__atomic_base<_IntTp>::__int_type std::__atomic_base<_IntTp>::load(std::memory_order) const [with _ITp = long unsigned int]', inlined from 'std::__atomic_base<_IntTp>::operator __int_type() const [with _ITp = long unsigned int]' at /opt/compiler-explorer/gcc-trunk-20230111/include/c++/13.0.0/bits/atomic_base.h:365:20, inlined from 'void f(std::shared_ptr<A>)' at <source>:13:69: /opt/compiler-explorer/gcc-trunk-20230111/include/c++/13.0.0/bits/atomic_base.h:505:31: error: 'long unsigned int __atomic_load_8(const volatile void*, int)' writing 8 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 505 | return __atomic_load_n(&_M_i, int(__m)); | ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~ In function 'void f(std::shared_ptr<A>)': cc1plus: note: destination object is likely at address zero cc1plus: some warnings being treated as errors Compiler returned: 1 I have found bug #104475 which seems to also deal with atomics and -Wstringop-overflow however I can't judge if it looks like a duplicate or a different issue. Cheers, Romain
next reply other threads:[~2023-01-11 18:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-11 18:18 romain.geissler at amadeus dot com [this message] 2023-01-11 18:19 ` [Bug tree-optimization/108374] " romain.geissler at amadeus dot com 2023-01-12 9:43 ` rguenth at gcc dot gnu.org 2023-01-12 9:57 ` redi at gcc dot gnu.org 2023-01-12 10:00 ` rguenth at gcc dot gnu.org 2023-01-12 10:10 ` redi at gcc dot gnu.org 2023-01-12 11:34 ` jakub at gcc dot gnu.org 2023-05-08 12:26 ` [Bug tree-optimization/108374] [12/13/14 " rguenth at gcc dot gnu.org
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-108374-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).