public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112087] New: gimple front end: Simple testcase with array fails to round trip
Date: Wed, 25 Oct 2023 14:08:12 +0000	[thread overview]
Message-ID: <bug-112087-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112087
           Summary: gimple front end: Simple testcase with array fails to
                    round trip
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: acoplan at gcc dot gnu.org
  Target Milestone: ---

Reproducer:

$ cat t.c
long f()
{
  int a[4];
  return (long)a;
}
$ gcc/xgcc -B gcc -c t.c -S -o /dev/null -O2 -fdump-tree-ssa-gimple=gimple.c
$ cat gimple.c
long int __GIMPLE (ssa)
f ()
{
  int a[4];
  long int _1;

  __BB(2):
  _1 = (long int) _Literal (int[4] *)&a;
  a ={v} _Literal (int[4]) {CLOBBER(eol)};
  return _1;

}


$ gcc/xgcc -B gcc -c gimple.c -S -o /dev/null -O2 -fgimple
gimple.c: In function ‘f’:
gimple.c:8:35: error: expected ‘)’ before ‘*’ token
    8 |   _1 = (long int) _Literal (int[4] *)&a;
      |                                   ^~
      |                                   )
gimple.c:9:6: error: expected expression before ‘{’ token
    9 |   a ={v} _Literal (int[4]) {CLOBBER(eol)};
      |      ^
gimple.c:12:1: error: invalid types in nop conversion
   12 | }
      | ^
long int
int[4]
_1 = (long int) &a;

             reply	other threads:[~2023-10-25 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 14:08 acoplan at gcc dot gnu.org [this message]
2023-10-27 12:57 ` [Bug middle-end/112087] " 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-112087-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).