From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-444377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 17903 invoked by alias); 20 Feb 2014 15:00:50 -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
Received: (qmail 17883 invoked by uid 48); 20 Feb 2014 15:00:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60271] [C++1y] std::max(initializer_list<T>) cannot use std::max_element
Date: Thu, 20 Feb 2014 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60271-4-dLHbfMcpiy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60271-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60271-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-02/txt/msg02134.txt.bz2

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Even if max_element() isn't made constexpr, we can make __max_element constexpr
(once the FE supports it) and use it directly in max.

It's certainly solvable, I just wanted to create this PR so we don't forget
about it.