public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51253] [C++11][DR 1030] Evaluation order (sequenced-before relation) among initializer-clauses in braced-init-list
Date: Thu, 13 Mar 2014 17:40:00 -0000	[thread overview]
Message-ID: <bug-51253-4-LqWlJDKhNr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51253-4@http.gcc.gnu.org/bugzilla/>

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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #9 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Akim Demaille from comment #6)
> FWIW, because of this issue, I no longer use g++ for my project, which
> saddens me.  If there were a means to put money on some bugs, I'd be happy
> to drop say $50.  I do not pretend that should suffice, but maybe other
> people would be happy to put money on their bugs, and maybe in end some bugs
> might be worth shooting at.  Sort of crowd-funding.  Of course it would
> require some infrastructure to support this, but maybe this would be worth
> considering?

It would be nice if such infrastructure existed. Perhaps it would motivate more
people to contribute to GCC (current contributors have their hands pretty full
already). I know of: https://www.bountysource.com/trackers/384568-gcc
but I have never used it, so I don't know how it works.
>From gcc-bugs-return-446210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Mar 13 17:49:48 2014
Return-Path: <gcc-bugs-return-446210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29598 invoked by alias); 13 Mar 2014 17:49:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29565 invoked by uid 48); 13 Mar 2014 17:49:44 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/60455] Imprecise column number of -Woverflow in array initializers
Date: Thu, 13 Mar 2014 17:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-60455-4-mK1KcwVSJO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60455-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60455-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg01079.txt.bz2
Content-length: 643

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`455

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2014-03-13
                 CC|                            |mpolacek at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |mpolacek at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Mine.


  parent reply	other threads:[~2014-03-13 17:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  4:24 [Bug c++/51253] New: [C++11][DR 1030] Evaluation order (sequenced-before relation) among intializer-clauses " ai.azuma at gmail dot com
2012-10-10  9:24 ` [Bug c++/51253] [C++11][DR 1030] Evaluation order (sequenced-before relation) among initializer-clauses " paolo.carlini at oracle dot com
2013-07-05 13:49 ` akim.demaille at gmail dot com
2013-07-05 15:06 ` paolo.carlini at oracle dot com
2013-08-13 17:07 ` broes.decat at gmail dot com
2013-10-23 16:38 ` st at quanttec dot com
2013-11-25 11:54 ` akim.demaille at gmail dot com
2014-01-18 16:12 ` akim.demaille at gmail dot com
2014-03-06 14:38 ` akim.demaille at gmail dot com
2014-03-13 17:07 ` paolo.carlini at oracle dot com
2014-03-13 17:40 ` manu at gcc dot gnu.org [this message]
2014-04-10  8:14 ` akim.demaille at gmail dot com
2014-04-11 17:09 ` jason at gcc dot gnu.org
2014-06-03  9:29 ` redi at gcc dot gnu.org
2014-06-04  1:11 ` redi at gcc dot gnu.org
2014-06-04  6:23 ` akim.demaille at gmail dot com
2014-06-04 15:51 ` jason at gcc dot gnu.org
2014-06-30 14:26 ` jason at gcc dot gnu.org
2014-07-01  8:20 ` christophe.lyon at st dot com
2014-07-03  2:11 ` jason at gcc dot gnu.org
2014-07-07 11:57 ` christophe.lyon at st dot com
2014-08-01 18:53 ` jason at gcc dot gnu.org
2014-08-06 18:36 ` dacamara.cameron at gmail dot com

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-51253-4-LqWlJDKhNr@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).