public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexandre dot nunes at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28755] [4.0/4.1/4.2 Regression] duplicate members of arrays
Date: Tue, 15 Jan 2008 19:13:00 -0000	[thread overview]
Message-ID: <20080115181214.15488.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28755-9416@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from alexandre dot nunes at gmail dot com  2008-01-15 18:12 -------
(In reply to comment #8)
> Fixed on the trunk.
> 

For anyone else wondering, this is still reproductible on vanilla gcc 4.2.2.


-- 


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


  parent reply	other threads:[~2008-01-15 18:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 17:28 [Bug c/28755] New: " dwmw2 at infradead dot org
2006-08-16 17:29 ` [Bug c/28755] " dwmw2 at infradead dot org
2006-08-16 17:36 ` [Bug middle-end/28755] " pinskia at gcc dot gnu dot org
2006-08-16 17:37 ` pinskia at gcc dot gnu dot org
2006-08-16 17:40 ` [Bug middle-end/28755] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-08-17 11:18 ` jakub at gcc dot gnu dot org
2006-08-20 22:49 ` mmitchel at gcc dot gnu dot org
2006-08-21  4:29 ` patchapp at dberlin dot org
2007-02-03 18:56 ` [Bug middle-end/28755] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org
2007-02-03 20:55 ` pinskia at gcc dot gnu dot org
2007-02-14  9:21 ` mmitchel at gcc dot gnu dot org
2007-09-23  9:35 ` jakub at gcc dot gnu dot org
2007-09-24  6:36 ` [Bug middle-end/28755] [4.0/4.1/4.2 " jakub at gcc dot gnu dot org
2008-01-15 19:13 ` alexandre dot nunes at gmail dot com [this message]
2008-07-04 21:28 ` [Bug middle-end/28755] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 17:04 ` 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=20080115181214.15488.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).