public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/21664] array-of-empty-structure extension not properly defined Date: Thu, 19 May 2005 20:20:00 -0000 [thread overview] Message-ID: <20050519202017.32262.qmail@sourceware.org> (raw) In-Reply-To: <20050519140009.21664.rguenth@gcc.gnu.org> ------- Additional Comments From rguenth at gcc dot gnu dot org 2005-05-19 20:20 ------- None. But I have to deal with the possibilities of these during folding of &a[2] == &a[1]. At least until the middle-end makes a promise that they cannot exist (which they do), or the C frontend rejects this. It's really a question for advice on details of our own extension to the C language. Richard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21664
next prev parent reply other threads:[~2005-05-19 20:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-19 14:02 [Bug c/21664] New: " rguenth at gcc dot gnu dot org 2005-05-19 19:45 ` Gabriel Dos Reis 2005-05-19 19:55 ` [Bug c/21664] " gdr at integrable-solutions dot net 2005-05-19 20:20 ` rguenth at gcc dot gnu dot org [this message] [not found] <bug-21664-10053@http.gcc.gnu.org/bugzilla/> 2005-10-25 19:47 ` pinskia at gcc dot gnu dot org [not found] <bug-21664-4@http.gcc.gnu.org/bugzilla/> 2014-03-20 7:27 ` mpolacek at gcc dot gnu.org 2014-04-18 20:57 ` mpolacek 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=20050519202017.32262.qmail@sourceware.org \ --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: linkBe 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).