From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 661B83856243; Tue, 30 May 2023 06:47:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 661B83856243 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685429256; bh=aXmEX/1rkZdmblkslpA6CtSSt5svh4WZPhDsQZcAEj8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yeUvXxY4Jzx9M0ua+533IlDUSAELLnnW1VCfwAW9Jrv5oKqhF/q1Iq1pwGTffOg0R K5U8dFUnr8kJgXY6CQ0UNxfloHhcikaw+tybrZUyY+Q5Wcq9lJx4QnW8TAI5M86off nz8wuhhqpYzkOQAbSu8wjFlMIDNiRr2b/GX/5aac= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110011] -mfull-toc (-mfp-in-toc) yields incorrect _Float128 constants on power9 Date: Tue, 30 May 2023 06:47:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.3.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status assigned_to 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110011 Kewen Lin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bergner at gcc dot gnu.org, | |gnu@the-meissners.org, | |linkw at gcc dot gnu.org, | |segher at gcc dot gnu.org Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gn= u.org --- Comment #3 from Kewen Lin --- Thanks for reporting, this exposes one issue that: when encoding KFmode constant into toc, it uses the format for the current long double, it could= be wrong if the current long double is with IBM format instead of IEEE format.= I have a patch.=