From: Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v7 2/8] Remove __morecore and __default_morecore
Date: Fri, 9 Jul 2021 12:32:14 +0530 [thread overview]
Message-ID: <d04dc07a-5253-9e73-f7aa-268fe372d249@sourceware.org> (raw)
In-Reply-To: <8735soknne.fsf@oldenburg.str.redhat.com>
On 7/9/21 11:57 AM, Florian Weimer via Libc-alpha wrote:
> * Siddhesh Poyarekar:
>
>> diff --git a/malloc/hooks.c b/malloc/hooks.c
>> index 45c91d6502..4aa6dadcff 100644
>> --- a/malloc/hooks.c
>> +++ b/malloc/hooks.c
>> @@ -20,6 +20,8 @@
>> #if SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_34)
>> void weak_variable (*__after_morecore_hook) (void) = NULL;
>> compat_symbol (libc, __after_morecore_hook, __after_morecore_hook, GLIBC_2_0);
>> +void *(*__morecore)(ptrdiff_t);
>> +compat_symbol (libc, __morecore, __morecore, GLIBC_2_0);
>> #endif
>
> This fails to assemble on ARC (and elsewhere with GCC 9 and earlier):
>
> /tmp/ccEXL6bz.s: Assembler messages:
> /tmp/ccEXL6bz.s: Error: `__morecore@GLIBC_2.32' can't be versioned to common sym
> bol '__morecore'
>
> You need to add __attribute__ ((morecore)).
I could do this (I know you mean nocommon there)...
> I posted a generic fix for this:
>
> Force building with -fno-common
> <https://sourceware.org/pipermail/libc-alpha/2021-July/128716.html>
>
> But until then, every instance needs to be fixed manually.
... or I could review your generic fix instead. It seems like a much
better cleanup than having to specify the attribute on everything that
changes. What do you think?
Siddhesh
next prev parent reply other threads:[~2021-07-09 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 17:43 [PATCH v7 0/8] malloc hooks removal Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 1/8] Remove __after_morecore_hook Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 2/8] Remove __morecore and __default_morecore Siddhesh Poyarekar via Libc-alpha
2021-07-09 6:27 ` Florian Weimer via Libc-alpha
2021-07-09 7:02 ` Siddhesh Poyarekar via Libc-alpha [this message]
2021-07-09 7:46 ` Florian Weimer via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 3/8] Move malloc hooks into a compat DSO Siddhesh Poyarekar via Libc-alpha
2021-07-09 8:08 ` Florian Weimer via Libc-alpha
2021-07-09 8:13 ` Siddhesh Poyarekar via Libc-alpha
2021-07-09 8:17 ` Florian Weimer via Libc-alpha
2021-07-09 9:17 ` Siddhesh Poyarekar via Libc-alpha
2021-07-09 9:22 ` Florian Weimer via Libc-alpha
2021-07-09 8:26 ` Florian Weimer via Libc-alpha
2021-07-09 9:21 ` Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 4/8] mcheck: Wean away from malloc hooks Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 5/8] Simplify __malloc_initialized Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 6/8] mtrace: Wean away from malloc hooks Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 7/8] glibc.malloc.check: " Siddhesh Poyarekar via Libc-alpha
2021-07-08 17:43 ` [PATCH v7 8/8] Remove " Siddhesh Poyarekar via Libc-alpha
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/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d04dc07a-5253-9e73-f7aa-268fe372d249@sourceware.org \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=siddhesh@sourceware.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).