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 target/48108] lto should be containerized in a single mach-o section on darwin
Date: Sun, 25 Sep 2011 09:57:00 -0000 [thread overview]
Message-ID: <bug-48108-4-zVY3c2X08Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48108-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48108
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #24958|0 |1
is obsolete| |
--- Comment #19 from Iain Sandoe <iains at gcc dot gnu.org> 2011-09-25 09:49:04 UTC ---
Created attachment 25359
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25359
wip 3
The new attachment implements the 'wrapper' in simple-object read and write and
darwin.c
Modulo checking comments/white space it's a candidate for fixing the bug.
I am not sure why this has been labelled 'enhancement' - we are generating
badly-formed mach-o (according to the vendor) - the fact that we don't see a
reported error with earlier vendor tool-chains doesn't seem to make it an
'enhancement' to get it right ;)
---
I've done --with-build-config='bootstrap-lto bootstrap-debug' (no Ada on trunk
because of unrelated issues) on:
trunk *-darwin9 (less Ada)
4.6 i686-darwin9 (incl. Ada) 4.6 powerpc-darwin9 is running.
trunk x86_64-darwin10 (less Ada)
4.6 x86_64-darwin10 (incl. Ada)
So - darwin 11 needs checking.
The patch applies cleanly to both 4.6 and trunk as of this time.
next prev parent reply other threads:[~2011-09-25 9:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 3:07 [Bug lto/48108] New: " howarth at nitro dot med.uc.edu
2011-03-14 3:10 ` [Bug lto/48108] " howarth at nitro dot med.uc.edu
2011-03-14 3:13 ` mikestump at comcast dot net
2011-03-14 9:01 ` iains at gcc dot gnu.org
2011-03-14 11:26 ` [Bug target/48108] " rguenth at gcc dot gnu.org
2011-03-14 23:34 ` mikestump at comcast dot net
2011-03-17 12:04 ` howarth at nitro dot med.uc.edu
2011-05-30 12:11 ` vincenzo.innocente at cern dot ch
2011-05-30 12:26 ` dominiq at lps dot ens.fr
2011-05-30 12:58 ` vincenzo.innocente at cern dot ch
2011-05-30 13:12 ` dominiq at lps dot ens.fr
2011-05-30 15:17 ` howarth at nitro dot med.uc.edu
2011-05-30 15:22 ` howarth at nitro dot med.uc.edu
2011-05-30 16:02 ` iains at gcc dot gnu.org
2011-07-07 10:23 ` iains at gcc dot gnu.org
2011-07-08 10:34 ` iains at gcc dot gnu.org
2011-07-08 11:20 ` howarth at nitro dot med.uc.edu
2011-07-10 4:41 ` fang at csl dot cornell.edu
2011-08-05 18:52 ` howarth at nitro dot med.uc.edu
2011-08-09 12:59 ` iains at gcc dot gnu.org
2011-09-25 9:57 ` iains at gcc dot gnu.org [this message]
2011-09-26 2:16 ` howarth at nitro dot med.uc.edu
2011-09-27 14:56 ` howarth at nitro dot med.uc.edu
2011-10-26 12:39 ` iains at gcc dot gnu.org
2011-10-26 13:29 ` howarth at nitro dot med.uc.edu
2011-11-13 16:10 ` iains at gcc dot gnu.org
2011-11-13 16:11 ` iains 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-48108-4-zVY3c2X08Q@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: 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).