public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nilsgladitz at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101118] New: coroutines: unexpected ODR warning for coroutine frame type in LTO builds Date: Fri, 18 Jun 2021 07:43:54 +0000 [thread overview] Message-ID: <bug-101118-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101118 Bug ID: 101118 Summary: coroutines: unexpected ODR warning for coroutine frame type in LTO builds Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nilsgladitz at gmail dot com Target Milestone: --- Created attachment 51033 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51033&action=edit Testcase source files The attached sources files are reduced from a C++ project using boost::asio and coroutines. I don't fully understand it but compiling them with vanilla GCC 11.1.0 like this: g++ -std=c++2a -fPIC -fcoroutines -Wall -flto -fno-fat-lto-objects -shared foo.cpp bar.cpp unexpectedly produces the following diagnostic: boost.hpp:81:3: warning: type ‘struct _ZN5boost4asio1gIiFviEE2abIiEENS0_9awaitableIiiEET_.frame’ violates the C++ One Definition Rule [-Wodr] 81 | } | ^ boost.hpp:81:3: note: a different type is defined in another translation unit 81 | } | ^ boost.hpp:79:34: note: the first difference of corresponding definitions is field ‘__D.9984.3.4’ 79 | template <typename k> static w ab(k ai) { | ^ boost.hpp:79:34: note: a field with different name is defined in another translation unit 79 | template <typename k> static w ab(k ai) { |
next reply other threads:[~2021-06-18 7:43 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-18 7:43 nilsgladitz at gmail dot com [this message] 2021-06-18 10:26 ` [Bug c++/101118] " rguenth at gcc dot gnu.org 2021-06-18 10:46 ` iains at gcc dot gnu.org 2021-06-18 15:18 ` nilsgladitz at gmail dot com 2021-06-18 15:39 ` iains at gcc dot gnu.org 2023-03-03 16:06 ` john at drouhard dot dev 2023-03-03 16:26 ` hubicka at gcc dot gnu.org 2023-03-03 16:33 ` iains at gcc dot gnu.org 2023-03-03 17:06 ` hubicka at ucw dot cz 2023-03-03 17:10 ` iains at gcc dot gnu.org 2023-03-03 19:21 ` iains at gcc dot gnu.org 2023-03-03 19:29 ` iains at gcc dot gnu.org 2023-03-03 20:59 ` iains at gcc dot gnu.org 2023-03-07 12:53 ` hubicka at ucw dot cz 2023-03-07 15:04 ` iains at gcc dot gnu.org 2023-03-07 16:18 ` hubicka at ucw dot cz 2023-03-07 16:27 ` iains at gcc dot gnu.org 2023-04-01 5:28 ` cvs-commit at gcc dot gnu.org 2023-04-30 8:27 ` cvs-commit at gcc dot gnu.org 2023-05-16 19:07 ` cvs-commit at gcc dot gnu.org 2023-05-16 19:11 ` iains 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-101118-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).