public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/19435] spurious warnings with nested array constructors
Date: Fri, 21 Jan 2005 14:36:00 -0000	[thread overview]
Message-ID: <20050121143636.13470.qmail@sourceware.org> (raw)
In-Reply-To: <20050114030747.19435.rfeany@mrv.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-01-21 14:36 -------
(In reply to comment #2)
> I have very similar situation but with even worse results:

The C++ problem is recorded in a different bug (that might have been my fault for not testing the C++ 
front-end), see PR 18327.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19435


  parent reply	other threads:[~2005-01-21 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14  3:08 [Bug c/19435] New: " rfeany at mrv dot com
2005-01-14  3:14 ` [Bug c/19435] " pinskia at gcc dot gnu dot org
2005-01-21 13:37 ` mmikucionis at gmail dot com
2005-01-21 14:31 ` mmikucionis at gmail dot com
2005-01-21 14:36 ` pinskia at gcc dot gnu dot org [this message]
2005-02-01 23:04 ` jsm28 at gcc dot gnu dot org
2005-04-14 22:25 ` jsm28 at gcc dot gnu dot 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=20050121143636.13470.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: 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).