public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/41529] LTO configuration should detect if the target is ELF
Date: Sat, 02 Jan 2010 14:16:00 -0000 [thread overview]
Message-ID: <20100102141604.29341.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41529-91@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from rguenth at gcc dot gnu dot org 2010-01-02 14:16 -------
Fixed. The way to support LTO on non-ELF targets is to wrap all LTO sections
in an ELF container that is wrapped in a native section. We then have to
have code to open a native object format section and direct libelf to parse
that section content.
The implementation difficulty is to use libelf to produce the ELF object file
and then get that included in the assembly for the native wrapper section.
Well - for 4.6 if anyone wants to work on this.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
Target Milestone|--- |4.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41529
next prev parent reply other threads:[~2010-01-02 14:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:33 [Bug lto/41529] New: " dnovillo at gcc dot gnu dot org
2009-10-03 22:16 ` [Bug lto/41529] " rguenth at gcc dot gnu dot org
2009-10-08 21:26 ` [Bug lto/41529] [4.5 Regression] " pinskia at gcc dot gnu dot org
2009-10-19 10:54 ` [Bug bootstrap/41529] " rguenth at gcc dot gnu dot org
2009-10-23 19:35 ` steven at gcc dot gnu dot org
2009-10-23 19:37 ` pinskia at gcc dot gnu dot org
2009-10-24 9:59 ` bonzini at gnu dot org
2009-10-24 11:57 ` [Bug bootstrap/41529] " rguenth at gcc dot gnu dot org
2009-10-24 14:50 ` pinskia at gcc dot gnu dot org
2010-01-02 12:01 ` rguenth at gcc dot gnu dot org
2010-01-02 13:25 ` davek at gcc dot gnu dot org
2010-01-02 13:43 ` rguenth at gcc dot gnu dot org
2010-01-02 13:51 ` davek at gcc dot gnu dot org
2010-01-02 13:56 ` rguenther at suse dot de
2010-01-02 14:00 ` davek at gcc dot gnu dot org
2010-01-02 14:14 ` rguenth at gcc dot gnu dot org
2010-01-02 14:16 ` rguenth at gcc dot gnu dot org [this message]
2010-01-02 14:33 ` davek at gcc dot gnu dot org
2010-01-02 15:04 ` joseph at codesourcery dot com
2010-01-02 15:20 ` davek at gcc dot gnu dot org
2010-01-17 15:08 ` davek at gcc dot gnu dot org
2010-01-17 15:48 ` rguenther at suse dot de
2010-01-17 16:01 ` davek 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=20100102141604.29341.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: link
Be 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).