From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 37F913952501; Wed, 22 Apr 2020 22:15:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37F913952501 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587593712; bh=yP2JZHK7Fv1n7psTHK1wtzW89na3R9wTZV0OZQ5OzhU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UAguspNuijW8xqKt5oZYNxswXxySHlFvDcTlyGDmdXRnoyjANdoZsPRCoVoJ/8+S8 7cw52zkrMpXPE5fahefkAHveA0iKd6pwkRc4T0A7hMe2LYFYZ8L/HluIBV7OGMG/DP CtZJ684M0kGGkV3dJJqKjh+gcsiUxE9JVw64P8CU= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/94702] std::unsequenced_policy should not be defined for C++17 Date: Wed, 22 Apr 2020 22:15:12 +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: 10.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rodgertq at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2020 22:15:12 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94702 --- Comment #2 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #1) > Another bug is that we don't support the __cpp_lib_execution macro, which > should have been updated to indicate this policy is supported. That has been fixed in g:aac39307e8f589dba231083a3e9aa3d0ff302837 so that __cpp_lib_execution is always defined to 201902L even in C++17, to reflect = that this policy is always defined. That way the feature test macro accurately describes our implementation.=