public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111975] gimple front end can't round-trip vectorized code
Date: Mon, 18 Dec 2023 14:40:18 +0000	[thread overview]
Message-ID: <bug-111975-4-xqsK4uNkzx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111975-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:88a398a487ee37f1fc7850740f2d94d895657646

commit r14-6662-g88a398a487ee37f1fc7850740f2d94d895657646
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Dec 18 13:40:46 2023 +0100

    middle-end/111975 - dump -> GIMPLE FE roundtrip improvements

    The following improves the manual work needed to make a -gimple dump
    valid input to the GIMPLE FE.  First of all it recognizes the 'sizetype'
    tree and dumps it as __SIZETYPE__, then it changes dumping vector types
    without name from 'vector(n) T' to 'T [[gnu::vector_size(n')]]' which
    we can parse in most relevant contexts (and that's shorter than
    using __attribute__).  Third it avoids a NULL_TREE TMR_STEP when
    it would be one, an optimization that's re-done when generating RTL.

            PR middle-end/111975
            * tree-pretty-print.cc (dump_generic_node): Dump
            sizetype as __SIZETYPE__ with TDF_GIMPLE.
            Dump unnamed vector types as T [[gnu::vector_size(n)]] with
            TDF_GIMPLE.
            * tree-ssa-address.cc (create_mem_ref_raw): Never generate
            a NULL STEP when INDEX is specified.

  parent reply	other threads:[~2023-12-18 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  9:39 [Bug middle-end/111975] New: " acoplan at gcc dot gnu.org
2023-10-25 13:03 ` [Bug middle-end/111975] " rguenth at gcc dot gnu.org
2023-10-25 13:04 ` rguenth at gcc dot gnu.org
2023-12-18 12:00 ` cvs-commit at gcc dot gnu.org
2023-12-18 14:40 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-18 14:41 ` 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-111975-4-xqsK4uNkzx@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).