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/66523] the new clang-based assembler in Xcode 7 on 10.11 fails on libobjc/NXConstStr.m
Date: Tue, 07 Jul 2015 07:50:00 -0000 [thread overview]
Message-ID: <bug-66523-4-jW8xAm2dWi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66523-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66523
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-07-07
Ever confirmed|0 |1
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #7)
> (In reply to mrs@gcc.gnu.org from comment #6)
> > Another proposal, any symbol with an 'L.*' spelling should be not so marked,
> > as these can never be used this way. Seems like we should have a predicate
> > to call before marking something as no dead strip and it should get rid of
> > all of them, including L.* symbols.
>
> that's pretty much what my comment says - however, what I want to check
> (when I get a spare ns) is whether ObjC should be emitting "l_xxx" symbols
> for these (i.e. linker-only-visible, but not preserved). If someone else
> has time to look before me, then fine :)
So, I had a look at what Apple gcc-4.2.1 and current TOT clang produce.
gcc-4.2.1 is silent about preservation.
clang puts the relevant stuff into sections marked as "no_dead_strip" (but
doesn't mark the individual symbols).
For LTO to work we need to mark these items as non-strippable, because that
happens in a way that won't see that the containing section is "no_dead_strip".
Thus, for now, I think that the patch I have in my Q is OK.
(as a follow-on, I think to revise the section headers to ensure that they
contain "no_dead_strip", but that needs to be checked to be compatible with the
range of ld64 variants we use).
The current patch does what Mike has suggested above - rejects symbols starting
with L* as no_dead_strip.
Any other opinions (or shall I post/apply the patch)?
next prev parent reply other threads:[~2015-07-07 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 15:05 [Bug target/66523] New: " howarth.at.gcc at gmail dot com
2015-06-12 15:11 ` [Bug target/66523] " howarth.at.gcc at gmail dot com
2015-06-15 15:00 ` kassafari at gmail dot com
2015-06-15 15:09 ` iains at gcc dot gnu.org
2015-06-19 23:36 ` howarth.at.gcc at gmail dot com
2015-07-01 14:04 ` howarth.at.gcc at gmail dot com
2015-07-05 18:11 ` mrs at gcc dot gnu.org
2015-07-05 18:39 ` iains at gcc dot gnu.org
2015-07-07 7:50 ` iains at gcc dot gnu.org [this message]
2015-07-07 16:02 ` mrs at gcc dot gnu.org
2015-07-07 18:57 ` howarth.at.gcc at gmail dot com
2015-07-07 19:04 ` mrs at gcc dot gnu.org
2015-07-08 15:13 ` howarth.at.gcc at gmail dot com
2015-07-08 16:57 ` mrs at gcc dot gnu.org
2015-07-08 17:00 ` mrs at gcc dot gnu.org
2015-07-08 17:20 ` mrs at gcc dot gnu.org
2015-07-09 2:15 ` howarth.at.gcc at gmail dot com
2015-07-09 16:08 ` howarth.at.gcc at gmail dot com
2015-07-09 17:51 ` mrs at gcc dot gnu.org
2015-07-09 17:56 ` mrs at gcc dot gnu.org
2015-07-09 18:00 ` mrs at gcc dot gnu.org
2015-07-09 19:28 ` howarth.at.gcc at gmail dot com
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-66523-4-jW8xAm2dWi@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).