public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "congli at smail dot nju.edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111811] New: gcc: internal compiler error: tree check: expected none of vector_type, have vector_type in finish_struct
Date: Sat, 14 Oct 2023 17:09:21 +0000	[thread overview]
Message-ID: <bug-111811-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111811
           Summary: gcc: internal compiler error: tree check: expected
                    none of vector_type, have vector_type in finish_struct
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: congli at smail dot nju.edu.cn
  Target Milestone: ---

Compiler explorer: https://godbolt.org/z/WWzcPWcqs.

The following program `small.c` triggers a crash in gcc-14:

``` sh
% cat small.c
struct A {
    __attribute__((__vector_size__(4))) float d : 1;
};


% gcc-tk -O0 small.c
<source>:2:47: error: bit-field 'd' has invalid type
    2 |     __attribute__((__vector_size__(4))) float d : 1;
      |                                               ^
<source>:3:1: internal compiler error: tree check: expected none of
vector_type, have vector_type in finish_struct, at c/c-decl.cc:9358
    3 | };
      | ^
0x22ff3ee internal_error(char const*, ...)
  ???:0
0x8a7b87 tree_not_check_failed(tree_node const*, char const*, int, char const*,
...)
  ???:0
0xa7ab0d c_parser_declspecs(c_parser*, c_declspecs*, bool, bool, bool, bool,
bool, bool, bool, c_lookahead_kind)
  ???:0
0xaa468d c_parse_file()
  ???:0
0xb17919 c_common_parse_file()
  ???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
```

GCC version:

```
gcc
(Compiler-Explorer-Build-gcc-300d7d3a8f4b53d045ce43f1ed4e10301781c786-binutils-2.40)
14.0.0 20231014 (experimental)
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```

             reply	other threads:[~2023-10-14 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14 17:09 congli at smail dot nju.edu.cn [this message]
2023-11-12 22:09 ` [Bug c/111811] [14 Regression] ICE with vector float bitfield after error pinskia at gcc dot gnu.org
2023-11-12 22:13 ` pinskia at gcc dot gnu.org
2023-11-13  9:57 ` rguenth at gcc dot gnu.org
2023-11-13 23:24 ` joseph at codesourcery dot com
2023-11-14  8:07 ` rguenther at suse dot de
2024-01-15 13:54 ` rguenth at gcc dot gnu.org
2024-05-07  7:42 ` [Bug c/111811] [14/15 " 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-111811-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).