From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 19C4E385DC0F; Tue, 14 Apr 2020 10:15:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 19C4E385DC0F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586859351; bh=s0nerZygxLThonwl4WM6Gq5oE0iqoIR2qv1vJGuUx4w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OzkbC6LyB3uzTPHPXgqDYLmEFscu7Kca8BuaDMShnPgZ9eLkJQNePSProiXD+JuA/ ZKxK30dQL2L6tisMg0ItpqQGCPksZBpXCDk3JtufVrzgaWP/0yaL+XB+pm1SsyXBRl eVwOl4RQA1nmTleTo+ef5tr2DM1A69EPl52J/oQA= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94590] Incorrectly accepts invalid C++11 braced initialisation of double from long double if sizeof(long double)==sizeof(double) Date: Tue, 14 Apr 2020 10:15:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: accepts-invalid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: keywords bug_status everconfirmed cf_reconfirmed_on 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: Tue, 14 Apr 2020 10:15:51 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94590 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2020-04-14 --- Comment #1 from Jonathan Wakely --- (In reply to Giuseppe D'Angelo from comment #0) > +++ This bug was initially created as a clone of Bug #92856 +++ >=20 > (Sorry, couldn't find a way to reopen _that_ bug, so creating a new one) Good, it's not the same bug. That one said we should give an error not a warning, which is wrong. This one says we should give a diagnostic irrespective of target, which is correct.=