public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/109828] C2x:static compound literal (with flexible array) in initializer leads to invalid size and ICE
Date: Fri, 12 May 2023 14:32:42 +0000	[thread overview]
Message-ID: <bug-109828-4-1sQwtJLaHw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109828-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Yann Droneaud <yann at droneaud dot fr> ---
(In reply to Yann Droneaud from comment #0)
> The following code is badly compiled by GCC 13.1:
> 
>     struct s { int i; char c[]; };
> 
>     const struct s s = { .c = "0", };
>     const struct s *r = &(constexpr struct s) { .c = "1", };
>     const struct s *t = &(static struct s) { .c = "2", };
> 
> Targetting x86-64 / amd64, compiling this with gcc -std=gnu2x -S, produces
> surprising large .zero directive:
> 
>     s: 
>         .zero   4
>         .string "0"
>     __compound_literal.0:
>         .zero   4
>         .string "1"
>         .zero   18446744073709551613
>         .zero   1
>     r:
>         .quad   __compound_literal.0
>     __compound_literal.1:
>         .zero   4
>         .string "2"
>         .zero   18446744073709551613
>         .zero   1
>     t:
>         .quad   __compound_literal.1
> 
>

When asked to assemble that, binutils' as complains:

    $ gcc -std=gnu2x nice.c -c
    /tmp/ccZEWv73.s: Assembler messages:
    /tmp/ccZEWv73.s:17: Warning: .space repeat count is zero, ignored
    /tmp/ccZEWv73.s:32: Warning: .space repeat count is zero, ignored

  parent reply	other threads:[~2023-05-12 14:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 12:42 [Bug c/109828] New: " yann at droneaud dot fr
2023-05-12 12:54 ` [Bug c/109828] " yann at droneaud dot fr
2023-05-12 14:32 ` yann at droneaud dot fr [this message]
2023-05-12 18:41 ` [Bug c/109828] [13/14 Regression] " pinskia at gcc dot gnu.org
2023-05-12 19:10 ` yann at droneaud dot fr
2023-05-12 19:16 ` pinskia at gcc dot gnu.org
2023-05-12 20:43 ` pinskia at gcc dot gnu.org
2023-05-15  6:47 ` [Bug c/109828] [13/14 Regression] static compound literal with flexible array " rguenth at gcc dot gnu.org
2023-05-15 12:38 ` yann at droneaud dot fr
2023-05-15 16:30 ` yann at droneaud dot fr
2023-07-27  9:26 ` rguenth at gcc dot gnu.org
2023-08-27 20:00 ` pinskia at gcc dot gnu.org
2024-01-10 17:28 ` jamborm at gcc dot gnu.org
2024-01-12 11:58 ` rguenth at gcc dot gnu.org
2024-05-21  9:15 ` [Bug c/109828] [13/14/15 " jakub 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-109828-4-1sQwtJLaHw@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).