From: vladimir.mezentsev@oracle.com
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: vladimir.mezentsev@oracle.com
Subject: Re: [PATCH] PR gcc/84923 - gcc.dg/attr-weakref-1.c failed on aarch64
Date: Thu, 17 May 2018 05:10:00 -0000 [thread overview]
Message-ID: <63e57d97-54f1-8e02-089e-8a282e2d2046@oracle.com> (raw)
In-Reply-To: <1526020226-13904-1-git-send-email-vladimir.mezentsev@oracle.com>
Ping.
-Vladimir
On 05/10/2018 11:30 PM, vladimir.mezentsev@oracle.com wrote:
> From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>
> When weakref_targets is not empty a target cannot be removed from the weak list.
> A small example is below when 'wv12' is removed from the weak list on aarch64:
> static vtype Wv12 __attribute__((weakref ("wv12")));
> extern vtype wv12 __attribute__((weak));
>
> Bootstrapped on aarch64-unknown-linux-gnu including (c,c++ and go).
> Tested on aarch64-linux-gnu.
> No regression. The attr-weakref-1.c test passed.
>
> ChangeLog:
> 2018-05-10 Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>
> PR gcc/84923
> * varasm.c (weak_finish): clean up weak_decls
> ---
> gcc/varasm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/varasm.c b/gcc/varasm.c
> index 85296b4..8cf6e1e 100644
> --- a/gcc/varasm.c
> +++ b/gcc/varasm.c
> @@ -5652,7 +5652,8 @@ weak_finish (void)
> tree alias_decl = TREE_PURPOSE (t);
> tree target = ultimate_transparent_alias_target (&TREE_VALUE (t));
>
> - if (! TREE_SYMBOL_REFERENCED (DECL_ASSEMBLER_NAME (alias_decl)))
> + if (! TREE_SYMBOL_REFERENCED (DECL_ASSEMBLER_NAME (alias_decl))
> + || TREE_SYMBOL_REFERENCED (target))
> /* Remove alias_decl from the weak list, but leave entries for
> the target alone. */
> target = NULL_TREE;
next prev parent reply other threads:[~2018-05-17 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 6:42 vladimir.mezentsev
2018-05-17 5:10 ` vladimir.mezentsev [this message]
2018-05-17 8:21 ` Kyrill Tkachov
2018-05-17 8:46 ` Richard Biener
2018-05-21 20:34 ` Jeff Law
2018-05-21 22:37 ` vladimir.mezentsev
-- strict thread matches above, loose matches on Subject: below --
2018-04-13 6:09 vladimir.mezentsev
2018-04-25 10:06 ` Ramana Radhakrishnan
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=63e57d97-54f1-8e02-089e-8a282e2d2046@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=gcc-patches@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).