public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/54025] atomic<chrono::duration> won't compile: chrono::duration::duration() is not C++11 compliant
Date: Thu, 19 Jul 2012 10:20:00 -0000	[thread overview]
Message-ID: <bug-54025-4-88Ue3TjwZy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54025-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-07-19 10:20:07 UTC ---
Yes, I think so.  I initially wondered if there was some interaction with PR
53901 but I think that just makes the bug visible, duration's constructor
should be explicitly-defaulted anyway.


  parent reply	other threads:[~2012-07-19 10:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  2:55 [Bug libstdc++/54025] New: " chip at pobox dot com
2012-07-19  2:57 ` [Bug libstdc++/54025] " chip at pobox dot com
2012-07-19  8:34 ` redi at gcc dot gnu.org
2012-07-19  9:40 ` paolo.carlini at oracle dot com
2012-07-19 10:20 ` redi at gcc dot gnu.org [this message]
2012-07-19 11:57 ` paolo.carlini at oracle dot com
2012-07-19 12:06 ` redi at gcc dot gnu.org
2012-07-19 12:08 ` redi at gcc dot gnu.org
2012-07-19 12:17 ` paolo.carlini at oracle dot com
2012-07-19 12:19 ` redi at gcc dot gnu.org
2012-07-19 12:23 ` paolo.carlini at oracle dot com
2012-07-19 12:34 ` redi at gcc dot gnu.org
2012-07-19 12:48 ` paolo.carlini at oracle dot com
2012-07-19 15:18 ` daniel.kruegler at googlemail dot com
2012-07-19 15:26 ` paolo.carlini at oracle dot com
2012-07-20  9:49 ` paolo at gcc dot gnu.org
2012-07-20  9:51 ` 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-54025-4-88Ue3TjwZy@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).