public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97382] New: STMT_VINFO_SAME_ALIGN_REFS should go away
Date: Mon, 12 Oct 2020 13:33:14 +0000	[thread overview]
Message-ID: <bug-97382-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97382

            Bug ID: 97382
           Summary: STMT_VINFO_SAME_ALIGN_REFS should go away
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

We record for each stmt info with a DR the set of DRs with "the same alignment"
and use that for quick counting and align adjustment in peeling for alignment.

We can do better & cheaper if we simply record the set of DRs which use the
same DR_BASE_ADDRESS, DR_OFFSET and DR_STEP.  We can then improve
adjusting DR_MISALIGNMENT even for not equal align refs based on
DR_INIT differences.

A single loop over DRs and a hash-map from the triple to a vector of DRs
local to vect_enhance_data_refs_alignment is probably better than the current
storage which is quadratic in size.

STMT_VINFO_SAME_ALIGN_REFS is one consumer that depends on the vector type
choosen for a DR and thus vect_update_shared_vectype and its problems.

             reply	other threads:[~2020-10-12 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 13:33 rguenth at gcc dot gnu.org [this message]
2020-10-12 13:56 ` [Bug tree-optimization/97382] " rguenth at gcc dot gnu.org
2020-10-13 13:02 ` cvs-commit at gcc dot gnu.org
2020-10-13 13:03 ` rguenth at gcc dot gnu.org

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=bug-97382-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).