public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/64860] [5 Regression] multiple definition of typeinfo in 5.0 (4.9.2 works) Date: Mon, 23 Mar 2015 04:33:00 -0000 [thread overview] Message-ID: <bug-64860-4-SC5Q0iYjFS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64860-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64860 --- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Created attachment 35100 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35100&action=edit partial patch Hi, this is a patch that adds necessary checks into resolution code. Basically if static linking is anticipated, we can not derive much of useful info from PREVAILING_DEF/PREVAILING_DEF_IRONLY_EXP and must anticipate that static linking may change these and drop comdat groups. THe catch is that someone needs to pass -r to lto1 that is not currently happening (I verified that if I hack opts.c to set incremental_linking to true the testcase works). With -r option, I can imagine that lto-wrapper can do it, because we get: COLLECT_GCC_OPTIONS='-c' '-fmath-errno' '-fsigned-zeros' '-ftrapping-math' '-fno-trapv' '-fno-openmp' '-fno-openacc' '-mtune=generic' '-march=x86-64' '-O2' '-B' './' '-O2' '-r' '-v' '-mtune=generic' '-march=x86-64' '-fltrans-output-list=/tmp/cc3o3UIr.ltrans.out' '-fwpa' '-fresolution=/tmp/cchYXuvF.res I donot know hwere -r gets dropped though. But the testcase uses -Wl,-r that may need LTO plugin extension?
next prev parent reply other threads:[~2015-03-23 1:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-64860-4@http.gcc.gnu.org/bugzilla/> 2015-01-29 15:27 ` rguenth at gcc dot gnu.org 2015-01-29 15:27 ` [Bug lto/64860] " rguenth at gcc dot gnu.org 2015-02-01 18:49 ` [Bug lto/64860] [5 Regression] " hubicka at gcc dot gnu.org 2015-02-02 6:31 ` hubicka at gcc dot gnu.org 2015-03-18 12:53 ` rguenth at gcc dot gnu.org 2015-03-18 18:30 ` hubicka at gcc dot gnu.org 2015-03-18 18:33 ` hubicka at gcc dot gnu.org 2015-03-23 4:33 ` hubicka at gcc dot gnu.org [this message] 2015-03-27 14:48 ` jakub at gcc dot gnu.org 2015-03-30 7:29 ` hubicka at gcc dot gnu.org 2015-04-22 12:06 ` [Bug lto/64860] [5/6 " jakub at gcc dot gnu.org 2015-07-16 9:20 ` 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-64860-4-SC5Q0iYjFS@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).