public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/51916] FAIL: gcc.dg/lto/trans-mem-3 c_lto_trans-mem-3_0.o-c_lto_trans-mem-3_1.o link, -flto (internal compiler error) Date: Sat, 21 Jan 2012 11:22:00 -0000 [thread overview] Message-ID: <bug-51916-4-Pk8EIefIPa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51916-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51916 --- Comment #9 from Iain Sandoe <iains at gcc dot gnu.org> 2012-01-21 10:34:59 UTC --- (In reply to comment #8) > (In reply to comment #7) > ... so this is a build/config issue - or, alternatively, the segment name can > be specified as above since it is ignored for non-mach-o platforms. note: gcc/lto/lto-object.c hardwires this without any ill effect on other platforms. So, since the test and the section are lto-specific, I'd suspect that this is the right solution rather than some tricky config machinery.
next prev parent reply other threads:[~2012-01-21 10:35 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-20 13:25 [Bug lto/51916] New: " dominiq at lps dot ens.fr 2012-01-20 15:52 ` [Bug lto/51916] " aldyh at gcc dot gnu.org 2012-01-20 16:26 ` dominiq at lps dot ens.fr 2012-01-20 16:50 ` aldyh at redhat dot com 2012-01-20 19:18 ` dominiq at lps dot ens.fr 2012-01-20 20:08 ` aldyh at redhat dot com 2012-01-21 0:01 ` dominiq at lps dot ens.fr 2012-01-21 0:03 ` patrick.marlier at gmail dot com 2012-01-21 10:56 ` iains at gcc dot gnu.org 2012-01-21 11:22 ` iains at gcc dot gnu.org [this message] 2012-01-23 10:24 ` rguenth at gcc dot gnu.org 2012-01-23 10:28 ` dominiq at lps dot ens.fr 2012-01-23 14:11 ` aldyh at gcc dot gnu.org 2012-01-23 14:44 ` aldyh 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-51916-4-Pk8EIefIPa@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).