public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yaghmour.shafik at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49813] [C++0x] sinh vs asinh vs constexpr
Date: Wed, 31 Dec 2014 15:00:00 -0000	[thread overview]
Message-ID: <bug-49813-4-trIhfKJKQV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49813-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49813

Shafik Yaghmour <yaghmour.shafik at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yaghmour.shafik at gmail dot com

--- Comment #59 from Shafik Yaghmour <yaghmour.shafik at gmail dot com> ---
The resolution of LWG 2013 changed:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3788.html#2013 and it
no longer gives implementation the freedom to treat standard library functions
as constexpr unless it is explicitly required. The new wording was included in
the draft standard since at least N3936.

Although a strict reading seems to leave some wiggle room the intention as
mentioned in the updated issue was to avoid "diverging library implementations,
as users may use SFINAE to observe different behavior from otherwise identical
code".


  parent reply	other threads:[~2014-12-31 15:00 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 10:33 [Bug c++/49813] New: " paolo.carlini at oracle dot com
2011-07-22 10:40 ` [Bug c++/49813] [C++0x] " rguenth at gcc dot gnu.org
2011-07-22 10:42 ` rguenth at gcc dot gnu.org
2011-07-22 10:50 ` rguenth at gcc dot gnu.org
2011-07-22 10:51 ` paolo.carlini at oracle dot com
2011-07-22 10:53 ` paolo.carlini at oracle dot com
2011-07-22 10:58 ` rguenther at suse dot de
2011-07-22 11:02 ` paolo.carlini at oracle dot com
2011-07-22 11:08 ` vincenzo.innocente at cern dot ch
2011-07-22 11:10 ` paolo.carlini at oracle dot com
2011-07-22 11:19 ` rguenther at suse dot de
2011-07-22 11:23 ` rguenther at suse dot de
2011-07-22 11:23 ` paolo.carlini at oracle dot com
2011-07-22 11:25 ` paolo.carlini at oracle dot com
2011-07-22 11:30 ` rguenther at suse dot de
2011-07-22 11:31 ` rguenth at gcc dot gnu.org
2011-07-22 11:41 ` paolo.carlini at oracle dot com
2011-07-22 11:45 ` rguenther at suse dot de
2011-07-22 12:32 ` paolo.carlini at oracle dot com
2011-07-22 14:43 ` jason at gcc dot gnu.org
2011-07-22 15:08 ` paolo.carlini at oracle dot com
2011-07-22 15:31 ` paolo.carlini at oracle dot com
2011-07-22 16:07 ` jason at gcc dot gnu.org
2011-07-22 16:49 ` vincenzo.innocente at cern dot ch
2011-07-22 17:17 ` paolo.carlini at oracle dot com
2011-07-24 14:56 ` daniel.kruegler at googlemail dot com
2011-07-25  5:12 ` jason at gcc dot gnu.org
2011-07-25 10:20 ` [Bug libstdc++/49813] " paolo.carlini at oracle dot com
2011-07-25 10:24 ` paolo.carlini at oracle dot com
2011-07-25 10:46 ` rguenth at gcc dot gnu.org
2011-07-25 10:51 ` [Bug c++/49813] " paolo.carlini at oracle dot com
2011-07-25 10:55 ` paolo.carlini at oracle dot com
2011-07-25 11:00 ` rguenther at suse dot de
2011-07-25 11:02 ` vincenzo.innocente at cern dot ch
2011-07-25 11:18 ` paolo.carlini at oracle dot com
2011-07-25 11:43 ` paolo.carlini at oracle dot com
2011-07-25 11:46 ` paolo.carlini at oracle dot com
2011-07-25 11:46 ` rguenther at suse dot de
2011-07-25 11:47 ` paolo.carlini at oracle dot com
2011-07-25 11:50 ` paolo.carlini at oracle dot com
2011-07-25 11:58 ` paolo.carlini at oracle dot com
2011-07-25 19:59 ` paolo.carlini at oracle dot com
2011-07-26  0:12 ` jason at gcc dot gnu.org
2011-07-26  0:27 ` jason at gcc dot gnu.org
2011-07-26  0:29 ` paolo.carlini at oracle dot com
2011-07-27 16:51 ` paolo.carlini at oracle dot com
2011-07-27 17:19 ` paolo.carlini at oracle dot com
2011-07-27 19:34 ` paolo at gcc dot gnu.org
2011-07-27 22:33 ` ghazi at gcc dot gnu.org
2011-07-27 22:56 ` paolo.carlini at oracle dot com
2011-07-27 23:15 ` ghazi at gcc dot gnu.org
2011-07-28  6:48 ` jakub at gcc dot gnu.org
2011-07-28  9:28 ` rguenther at suse dot de
2011-07-28 21:01 ` sje at gcc dot gnu.org
2011-08-01 18:16 ` jason at gcc dot gnu.org
2011-08-01 18:28 ` jason at gcc dot gnu.org
2011-08-01 19:27 ` paolo at gcc dot gnu.org
2011-08-11 17:34 ` paolo.carlini at oracle dot com
2011-09-21  1:21 ` paolo.carlini at oracle dot com
2014-12-31 15:00 ` yaghmour.shafik at gmail dot com [this message]
2020-03-11 16:31 ` redi at gcc dot gnu.org
2020-03-11 16:39 ` jakub at gcc dot gnu.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=bug-49813-4-trIhfKJKQV@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).