public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "JamesMikeDuPont at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45853] Segfault while experimenting with c++-0x initializer lists
Date: Mon, 16 May 2011 20:51:00 -0000 [thread overview]
Message-ID: <bug-45853-4-6W1ykiGMhW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45853-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45853
--- Comment #5 from James Michael DuPont <JamesMikeDuPont at googlemail dot com> 2011-05-16 19:17:06 UTC ---
Ok,
I will have to look into it,
thanks,
mike
On Mon, May 16, 2011 at 1:19 PM, redi at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45853
>
> Jonathan Wakely <redi at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |WAITING
> Last reconfirmed| |2011.05.16 11:00:14
> Ever Confirmed|0 |1
>
> --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-05-16 11:00:14 UTC ---
> please try to reproduce this with a current FSF release or report it to Ubuntu
>
> for C++0x bugs please try 4.5 or later, lots of initializer list bugs have been
> fixed already
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
next prev parent reply other threads:[~2011-05-16 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 6:19 [Bug c++/45853] New: " JamesMikeDuPont at googlemail dot com
2010-10-01 7:24 ` [Bug c++/45853] " redi at gcc dot gnu.org
2011-05-16 11:16 ` redi at gcc dot gnu.org
2011-05-16 20:51 ` JamesMikeDuPont at googlemail dot com [this message]
2011-05-17 11:56 ` redi at gcc dot gnu.org
2011-09-23 12:31 ` paolo.carlini at oracle 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-45853-4-6W1ykiGMhW@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).