public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek 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: Sun, 17 Jan 2010 15:08:00 -0000	[thread overview]
Message-ID: <20100117150819.25232.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41529-91@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from davek at gcc dot gnu dot org  2010-01-17 15:08 -------
Created an attachment (id=19635)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19635&action=view)
lto for cygwin, and probably other coff targets

FTR.  Well, that turned out to be quite easy.  Needs some support in binutils
to allow us to override the default section alignment for object files, but
that's trivial, and I'll send it to the binutils list shortly.

Sigh, most of this is almost-safe-enough-for-stage-3.  Oh well.

Should I reopen this bug, assign it to myself, retarget it to 4.6 and add the
words "or COFF" to the summary?

Results from this patch:

Running /gnu/gcc/gcc/gcc/testsuite/gcc.dg/lto/lto.exp ...
FAIL: gcc.dg/lto/20081222 c_lto_20081222_1.o assemble, -O0 -fwhopr
FAIL: gcc.dg/lto/20081222 c_lto_20081222_1.o assemble, -O2 -fwhopr
FAIL: gcc.dg/lto/20081222 c_lto_20081222_1.o assemble, -O0 -flto
FAIL: gcc.dg/lto/20081222 c_lto_20081222_1.o assemble, -O2 -flto
FAIL: gcc.dg/lto/20090914-2 c_lto_20090914-2_0.o assemble, -O0 -fwhopr
FAIL: gcc.dg/lto/20090914-2 c_lto_20090914-2_0.o assemble, -O2 -fwhopr
FAIL: gcc.dg/lto/20090914-2 c_lto_20090914-2_0.o assemble, -O0 -flto
FAIL: gcc.dg/lto/20090914-2 c_lto_20090914-2_0.o assemble, -O2 -flto

                === gcc Summary ===

# of expected passes            462
# of unexpected failures        8
# of unresolved testcases       16
# of unsupported tests          2
/gnu/gcc/obj-lto/gcc/xgcc  version 4.5.0 20100116 (experimental) (GCC)

... i.e. the only tests that still fail are one that uses visibility and one
that has an ELF-specific .section directive in an asm, all the rest work and in
particular the "gcc.dg/lto/20081201-2 c_lto_20081201-2_0.o-c_lto_20081201-2_1.o
execute -O3 -fwhopr" test succeeds which indicates real LTO is taking place :-)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41529


  parent reply	other threads:[~2010-01-17 15:08 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
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 [this message]
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=20100117150819.25232.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).