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 target/65581] [5 Regression] testsuite lto issue: multiple definition of `main', undefined reference to `WinMain' Date: Wed, 01 Apr 2015 23:18:00 -0000 [thread overview] Message-ID: <bug-65581-4-JtnNmP9cKN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65581-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65581 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Hmm, is it still a problem and if so, why it is marked as resolved/invalid? crtbegin/crtend should be compiled without LTO even with LTO bootstrap. Can you post the callgraph and resolution file created by compiling the testcase with --save-temps and -fdump-ipa-cgraph?
next prev parent reply other threads:[~2015-04-01 23:18 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-26 12:27 [Bug target/65581] New: " rainer@emrich-ebersheim.de 2015-03-26 12:33 ` [Bug target/65581] [5 Regression] " rainer@emrich-ebersheim.de 2015-03-26 12:43 ` rguenth at gcc dot gnu.org 2015-03-26 12:43 ` rguenth at gcc dot gnu.org 2015-03-26 12:59 ` rainer@emrich-ebersheim.de 2015-03-26 15:49 ` ktietz at gcc dot gnu.org 2015-04-01 14:51 ` rainer@emrich-ebersheim.de 2015-04-01 23:18 ` hubicka at gcc dot gnu.org [this message] 2015-04-02 9:06 ` rainer@emrich-ebersheim.de 2015-04-02 9:07 ` rainer@emrich-ebersheim.de 2015-04-02 16:29 ` hubicka at gcc dot gnu.org 2015-04-02 18:42 ` rainer@emrich-ebersheim.de 2015-04-02 23:31 ` hubicka at gcc dot gnu.org 2015-04-03 9:23 ` rainer@emrich-ebersheim.de 2015-04-04 21:59 ` rainer@emrich-ebersheim.de 2015-04-06 18:41 ` rainer@emrich-ebersheim.de
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-65581-4-JtnNmP9cKN@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).