public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/93369] [10 regression] g++.dg/lto/pr64076 fails Date: Thu, 26 Mar 2020 12:07:05 +0000 [thread overview] Message-ID: <bug-93369-4-g4sGDfWDuW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93369-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93369 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #16 from Martin Liška <marxin at gcc dot gnu.org> --- I see the ODR warning being properly printed: g++ pr64076_0.o pr64076_1.o pr64076.H:10:8: warning: type ‘struct S’ violates the C++ One Definition Rule [-Wodr] 10 | struct S : public X, public Y, public Z | ^ pr64076.H:10:8: note: a type with the same name but different number of polymorphic bases is defined in another translation unit 10 | struct S : public X, public Y, public Z | ^ pr64076.H:8:8: note: the extra base is defined here 8 | struct T : public Base { }; | ^ pr64076.H:15:8: warning: type of ‘f’ does not match original declaration [-Wlto-type-mismatch] 15 | void f() | ^ pr64076_1.C:5:6: note: ‘f’ was previously declared here 5 | void S::f() { } | ^ pr64076_1.C:5:6: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used I agree with Honza that it's not P1.
next prev parent reply other threads:[~2020-03-26 12:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93369-4@http.gcc.gnu.org/bugzilla/> 2020-03-19 21:44 ` hubicka at gcc dot gnu.org 2020-03-26 12:07 ` marxin at gcc dot gnu.org [this message] 2020-04-04 10:11 ` hubicka at gcc dot gnu.org 2020-04-09 8:47 ` rguenth at gcc dot gnu.org 2020-04-09 11:28 ` hubicka at gcc dot gnu.org 2020-04-09 11:59 ` cvs-commit at gcc dot gnu.org 2020-04-09 11:59 ` 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-93369-4-g4sGDfWDuW@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).