public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-4938] ipa: Do not require RECORD_TYPE for ancestor jump functions
Date: Fri,  5 Nov 2021 13:31:00 +0000 (GMT)	[thread overview]
Message-ID: <20211105133100.EFCC63858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:ea42c80585b831fc4f7a0b2576a3d8d3244d8d32

commit r12-4938-gea42c80585b831fc4f7a0b2576a3d8d3244d8d32
Author: Martin Jambor <mjambor@suse.cz>
Date:   Fri Nov 5 14:04:42 2021 +0100

    ipa: Do not require RECORD_TYPE for ancestor jump functions
    
    The check this patch removes has remained from times when ancestor
    jump functions have been only used for devirtualization and also
    contained BINFOs.  It is not necessary now and should have been
    removed long time ago.
    
    gcc/ChangeLog:
    
    2021-11-04  Martin Jambor  <mjambor@suse.cz>
    
            * ipa-prop.c (compute_complex_assign_jump_func): Remove
            unnecessary check for RECORD_TYPE.

Diff:
---
 gcc/ipa-prop.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/gcc/ipa-prop.c b/gcc/ipa-prop.c
index 443f21ce61b..e85df0971fc 100644
--- a/gcc/ipa-prop.c
+++ b/gcc/ipa-prop.c
@@ -1421,8 +1421,6 @@ compute_complex_assign_jump_func (struct ipa_func_body_info *fbi,
   if (TREE_CODE (op1) != ADDR_EXPR)
     return;
   op1 = TREE_OPERAND (op1, 0);
-  if (TREE_CODE (TREE_TYPE (op1)) != RECORD_TYPE)
-    return;
   base = get_ref_base_and_extent_hwi (op1, &offset, &size, &reverse);
   offset_int mem_offset;
   if (!base


                 reply	other threads:[~2021-11-05 13:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211105133100.EFCC63858D28@sourceware.org \
    --to=jamborm@gcc.gnu.org \
    --cc=gcc-cvs@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).