public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/39316] [lto] revision 144454 - Configure should check for elf support (similar to gmp/mpfr/PPL/CLooG) Date: Sat, 03 Oct 2009 23:57:00 -0000 [thread overview] Message-ID: <20091003235705.3963.qmail@sourceware.org> (raw) In-Reply-To: <bug-39316-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from zadeck at naturalbridge dot com 2009-10-03 23:57 ------- Richard, the problem is that at least for the linux world there are two elf implementations that while they claim to be compatible are distinctly different on the inside. LTO, for better or worse, needs to use features that are not necessarily part of the "standard" elf, for some definition of standard. unlike gmp and mpfr, where there has always been 1 open source version, elf was reverse engineered for linux from the sun version at least twice, each with its own warts. It has not helped anything that suse and redhat seem to have chosen to distribute different implementations. this led to a fair amount of confusion when mark mitchell and i started working on lto because codesourcery generally runs redhat and naturalbridge runs suse. We were always breaking the code on the others machines. i think that iant "solved" this problem for gold by just writing his own elf library rather than relying on what was installed which is what lto does. Aside from going down that road, we are most likely screwed because lto needs stuff out of the mainstream elf. I hope that this clarifies some of your issues here. kenny -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39316
next prev parent reply other threads:[~2009-10-03 23:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-26 22:47 [Bug bootstrap/39316] New: " rob1weld at aol dot com 2009-02-26 23:45 ` [Bug bootstrap/39316] " rob1weld at aol dot com 2009-07-08 6:18 ` bje at gcc dot gnu dot org 2009-07-15 0:52 ` bje at gcc dot gnu dot org 2009-10-03 22:08 ` rguenth at gcc dot gnu dot org 2009-10-03 23:57 ` zadeck at naturalbridge dot com [this message] 2009-10-04 9:15 ` rguenth at gcc dot gnu dot org 2009-10-04 10:25 ` rob1weld at aol dot com 2009-10-04 10:32 ` rguenth at gcc dot gnu dot 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=20091003235705.3963.qmail@sourceware.org \ --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).