public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/105713] New: [gimplefe] need a way to specify TREE_ADDRESSABLE
@ 2022-05-24  8:08 rguenth at gcc dot gnu.org
  2022-05-24  8:08 ` [Bug c/105713] " rguenth at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-05-24  8:08 UTC (permalink / raw)
  To: gcc-bugs

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-05-18  5:59 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-24  8:08 [Bug c/105713] New: [gimplefe] need a way to specify TREE_ADDRESSABLE rguenth at gcc dot gnu.org
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

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).