public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65673] [9/10/11/12 Regression] Compound literal with initializer for zero-sized array drops other initializers
Date: Mon, 03 Jan 2022 20:34:08 +0000	[thread overview]
Message-ID: <bug-65673-4-KMFE3ZkiJx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65673-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Compound literal with       |[9/10/11/12 Regression]
                   |initializer for zero-sized  |Compound literal with
                   |array drops other           |initializer for zero-sized
                   |initializers                |array drops other
                   |                            |initializers
      Known to work|                            |4.1.2
      Known to fail|                            |4.4.7
   Target Milestone|---                         |9.5
           Keywords|                            |wrong-code

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
GCC 4.1.2 produces:

foo:
        .long   25
        .zero   4
        .quad   __compound_literal.0
        .local  __compound_literal.0
        .comm   __compound_literal.0,0,8

While 4.4.7 (and above) produces:
foo:
        .zero   16

  parent reply	other threads:[~2022-01-03 20:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05  6:42 [Bug c/65673] New: " stilor at att dot net
2015-04-17  7:09 ` [Bug c/65673] " mpolacek at gcc dot gnu.org
2015-04-17 13:03 ` mpolacek at gcc dot gnu.org
2022-01-03 20:34 ` pinskia at gcc dot gnu.org [this message]
2022-01-17 15:19 ` [Bug c/65673] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug c/65673] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2022-12-20 13:00 ` rguenth at gcc dot gnu.org
2023-01-31  1:29 ` luangruo at yahoo dot com
2023-07-07 10:30 ` [Bug c/65673] [11/12/13/14 " 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-65673-4-KMFE3ZkiJx@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).