From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: -znocombreloc?
Date: Sun, 4 Dec 2016 09:14:10 -0800 [thread overview]
Message-ID: <847afae4-9f9d-bcb0-b416-f076b0062eb2@dancol.org> (raw)
In-Reply-To: <83lgvvlndb.fsf@gnu.org>
On 12/04/2016 07:34 AM, Eli Zaretskii wrote:
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Sat, 3 Dec 2016 21:36:49 -0800
>>
>> https://lists.gnu.org/archive/html/bug-gnu-emacs/2004-02/msg00278.html
>> https://lists.gnu.org/archive/html/help-gnu-emacs/2003-05/msg00627.html
>>
>> Looking at recent GCC documentation it appears that this old hack should not
>> matter now, so I'm inclined to remove it, as in the proposed patch (attached),
>> which I tested on Fedora 24 x86-64 but have not installed.
>
> What about other systems: Solaris, *BSD (when they use GNU ld)? Do
> they also not need this?
In any case, my guess would be that other systems won't need this switch
with pdumper (because with pdumper, we won't be doing anything magical),
so locally, I'll just make this stuff conditional on !CANNOT_DUMP.
next prev parent reply other threads:[~2016-12-04 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 0:12 -znocombreloc? Daniel Colascione
2016-12-04 5:36 ` -znocombreloc? Paul Eggert
2016-12-04 10:36 ` -znocombreloc? Richard Copley
2016-12-04 11:24 ` -znocombreloc? Richard Copley
2016-12-04 15:34 ` -znocombreloc? Eli Zaretskii
2016-12-04 17:14 ` Daniel Colascione [this message]
2016-12-05 2:47 ` -znocombreloc? Paul Eggert
2016-12-07 23:58 ` -znocombreloc? Jeremie Courreges-Anglas
2016-12-08 1:19 ` -znocombreloc? Paul Eggert
-- strict thread matches above, loose matches on Subject: below --
2016-12-05 3:23 -znocombreloc? Ali Bahrami
2016-12-05 15:50 ` -znocombreloc? Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=847afae4-9f9d-bcb0-b416-f076b0062eb2@dancol.org \
--to=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).