public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@kam.mff.cuni.cz>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>
Subject: Re: [PATCH] ipa-icf: skip variables with body_removed
Date: Thu, 19 May 2022 17:02:07 +0200	[thread overview]
Message-ID: <YoZb755B4GulXM6D@kam.mff.cuni.cz> (raw)
In-Reply-To: <1cf184b6-a0a1-7514-37e1-ddd8c6b7d7e3@suse.cz>

> Similarly to cgraph_nodes, it may happen that body_removed is set
> during merging of symbols.
> 
> 	PR ipa/105600
> 
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
> 
> Ready to be installed?
> Thanks,
> Martin
> 
> gcc/ChangeLog:
> 
> 	* ipa-icf.cc (sem_item_optimizer::filter_removed_items):
> 	Skip variables with body_removed.
> ---
>  gcc/ipa-icf.cc | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/gcc/ipa-icf.cc b/gcc/ipa-icf.cc
> index 765ae746745..6528a7a10b2 100644
> --- a/gcc/ipa-icf.cc
> +++ b/gcc/ipa-icf.cc
> @@ -2411,10 +2411,11 @@ sem_item_optimizer::filter_removed_items (void)
>  	    {
>  	      /* Filter out non-readonly variables.  */
>  	      tree decl = item->decl;
> -	      if (TREE_READONLY (decl))
> -		filtered.safe_push (item);
> -	      else
> +	      varpool_node *vnode = static_cast <sem_variable *>(item)->get_node ();
> +	      if (!TREE_READONLY (decl) || vnode->body_removed)
>  		remove_item (item);
> +	      else
> +		filtered.safe_push (item);

So the situation here is that we merge symbols but keep syntactic alias
because the declarations are not compatible (have different attributes
perhaps because of fortify source)?

Will ICF still see through the aliases and do merging?  I think you can
craft a testcase by triggering the attribute mismatch and see what
happens.  At the time we implemented ICF these aliases did not exists,
so maybe some TLC is needed here.

Honza

  reply	other threads:[~2022-05-19 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  7:08 Martin Liška
2022-05-19 15:02 ` Jan Hubicka [this message]
2022-05-20  7:46   ` Martin Liška
2022-06-16  6:21     ` Martin Liška
2022-06-22 10:56       ` Jan Hubicka

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=YoZb755B4GulXM6D@kam.mff.cuni.cz \
    --to=hubicka@kam.mff.cuni.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    --cc=mliska@suse.cz \
    /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).