public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/56115] Internal compiler error / unable to generate a relocatable output with object file(which is with lto info). Date: Sat, 26 Jan 2013 15:25:00 -0000 [thread overview] Message-ID: <bug-56115-4-itrR7eKs15@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56115-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56115 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |lto Target| |arm-eabi Host| |i?86-linux --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-26 15:25:13 UTC --- Yes, quite possible. Add -O2 at link time.
next prev parent reply other threads:[~2013-01-26 15:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-26 2:38 [Bug c/56115] New: " tanjinfa at huawei dot com 2013-01-26 2:41 ` [Bug c/56115] " tanjinfa at huawei dot com 2013-01-26 2:46 ` [Bug lto/56115] " pinskia at gcc dot gnu.org 2013-01-26 15:25 ` rguenth at gcc dot gnu.org [this message] 2013-02-19 23:37 ` ramana 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-56115-4-itrR7eKs15@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).