From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Turn ___brk_addr into a compat symbol
Date: Tue, 24 Nov 2020 07:33:19 -0800 [thread overview]
Message-ID: <CAMe9rOrDtLth2F7Fbpymm9Mekm9h12FQcKiDq_Z4FGq7SBQzMw@mail.gmail.com> (raw)
In-Reply-To: <mvmlfeqak34.fsf@suse.de>
On Tue, Nov 24, 2020 at 6:46 AM Andreas Schwab <schwab@suse.de> wrote:
>
> On Nov 24 2020, H.J. Lu wrote:
>
> > Do any targets, except for i386-linux, ever reference this symbol?
>
> See gcc commit bced43dd6ca.
>
> Andreas.
>
I don't see references to ___brk_addr for ia64 nor microblaze since they were
added after
commit d0f8fcea2689a8c9c32648370c14e0ce40288bfa
Author: Richard Kenner <kenner@gcc.gnu.org>
Date: Fri Jun 28 14:08:53 1996 -0400
(init_dummy): Only i386-linux (at most) needs ___brk_addr hack.
I think ___brk_addr should be removed for ia64 and microblaze.
--
H.J.
next prev parent reply other threads:[~2020-11-24 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 13:34 Andreas Schwab
2020-11-24 13:41 ` H.J. Lu
2020-11-24 14:46 ` Andreas Schwab
2020-11-24 15:33 ` H.J. Lu [this message]
2020-11-24 15:43 ` Andreas Schwab
2020-11-24 15:56 ` H.J. Lu
2020-11-24 16:13 ` Andreas Schwab
2020-11-24 17:16 ` H.J. Lu
2020-11-25 11:15 ` Andreas Schwab
2020-12-02 11:21 ` Florian Weimer
2020-12-08 11:43 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2020-11-19 10:32 Andreas Schwab
2020-11-19 11:34 ` Florian Weimer
2020-11-19 12:25 ` Adhemerval Zanella
2020-11-19 14:57 ` Florian Weimer
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=CAMe9rOrDtLth2F7Fbpymm9Mekm9h12FQcKiDq_Z4FGq7SBQzMw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).