'[llvm-bugs] [Bug 46524] New: [Scalarizer] Handling of variable insert/extracts?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       llvm-bugs
Subject:    [llvm-bugs] [Bug 46524] New: [Scalarizer] Handling of variable insert/extracts?
From:       via llvm-bugs <llvm-bugs () lists ! llvm ! org>
Date:       2020-06-30 19:34:49
Message-ID: bug-46524-206 () http ! bugs ! llvm ! org/
[Download RAW message or body]

--1593545689.85003dC50.25588
Date: Tue, 30 Jun 2020 12:34:49 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.llvm.org/
Auto-Submitted: auto-generated

https://bugs.llvm.org/show_bug.cgi?id=46524

            Bug ID: 46524
           Summary: [Scalarizer] Handling of variable insert/extracts?
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Scalar Optimizations
          Assignee: unassignedbugs@nondot.org
          Reporter: lebedev.ri@gmail.com
                CC: llvm-bugs@lists.llvm.org

Currently, Scalarizer does not handle variable insert/extract,
and a `@f12` test in basic.ll suggests that is not an omission per-se.

Question: is this an intentional design decision,
or would it be acceptable to implement it?

I maybe might want to explore adding Scalarizer into default pipeline,
limited to <=2 elt vectors.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
--1593545689.85003dC50.25588
Date: Tue, 30 Jun 2020 12:34:49 -0700
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.llvm.org/
Auto-Submitted: auto-generated

<html>
    <head>
      <base href="https://bugs.llvm.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [Scalarizer] Handling of variable insert/extracts?"
   href="https://bugs.llvm.org/show_bug.cgi?id=46524">46524</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[Scalarizer] Handling of variable insert/extracts?
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>libraries
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>trunk
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Scalar Optimizations
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedbugs&#64;nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>lebedev.ri&#64;gmail.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs&#64;lists.llvm.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Currently, Scalarizer does not handle variable insert/extract,
and a `&#64;f12` test in basic.ll suggests that is not an omission per-se.

Question: is this an intentional design decision,
or would it be acceptable to implement it?

I maybe might want to explore adding Scalarizer into default pipeline,
limited to &lt;=2 elt vectors.</pre>
        </div>
      </p>

      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>
--1593545689.85003dC50.25588--

[Attachment #3 (text/plain)]

_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[prev in list] [next in list] [prev in thread] [next in thread] 