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 c/105713] New: [gimplefe] need a way to specify TREE_ADDRESSABLE
Date: Tue, 24 May 2022 08:08:11 +0000	[thread overview]
Message-ID: <bug-105713-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105713
           Summary: [gimplefe] need a way to specify TREE_ADDRESSABLE
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

For PR105711 a RTL expansion GIMPLE testcase would have been nice:

typedef char v2qi __attribute__((vector_size(2)));

void __GIMPLE (ssa,startwith("optimized"))
foo (__complex__ char c)
{
  __BB(2):
  __MEM <v2qi, 8> (&c) = _Literal (v2qi) { _Literal (char) 0, _Literal (char) 0
};
  return;
}

but here 'c' ends up TREE_ADDRESSABLE while with the original setup it is not.
That's because the C FE parsing marks 'c' addressable when parsing &c.  The
GIMPLE FE should fix this up on the optimistic side somehow and allow
specifying TREE_ADDRESSABLE at the declaration.

             reply	other threads:[~2022-05-24  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  8:08 rguenth at gcc dot gnu.org [this message]
2022-05-24  8:08 ` [Bug c/105713] " rguenth at gcc dot gnu.org
2023-05-17 23:23 ` pinskia at gcc dot gnu.org
2023-05-18  5:59 ` 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-105713-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).