From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F3E003858419; Wed, 8 Nov 2023 00:22:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F3E003858419 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1699402926; bh=/MnVo/ns9ulkwyjNzEtFtB2SvWTEYjxS+HddQr25Qlw=; h=From:To:Subject:Date:From; b=fpG4CYTmGVIfL8FoPI33QYq2N6lESQQYu+RjTBhZOfAAqaDPEbcDUSvAk2YIwJ+sM b8VcGO57lyq82+U6Ilmwfw9xBZ5wCaYT0M5NwqV90N0Qvt3iPEgD6rh/oNYSIHsYv/ 3e7QM58NWoFrGyMVTPxULG7bWVGOyrHp1SyWP7Dw= From: "pan2.li at intel dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/112432] New: Internal-fn: The [i|l|ll]rint family don't support FLOATN Date: Wed, 08 Nov 2023 00:21:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pan2.li at intel dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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=3D112432 Bug ID: 112432 Summary: Internal-fn: The [i|l|ll]rint family don't support FLOATN Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pan2.li at intel dot com Target Milestone: --- The [i|l|ll]rint family are defined as DEF_INTERNAL_FLT_FN instead of DEF_INTERNAL_FLT_FLOATN_FN in the internal-fn.def. Thus, the standard name = like lrint cannot be expanded when _Float16 type is given. Is there any reason/background that [i|l|ll]rint can honor FLOATN or not? L= ist all related fn definition as below. DEF_INTERNAL_FLT_FN (ICEIL, ECF_CONST, lceil, unary_convert) DEF_INTERNAL_FLT_FN (IFLOOR, ECF_CONST, lfloor, unary_convert) DEF_INTERNAL_FLT_FN (IRINT, ECF_CONST, lrint, unary_convert) DEF_INTERNAL_FLT_FN (IROUND, ECF_CONST, lround, unary_convert) DEF_INTERNAL_FLT_FN (LCEIL, ECF_CONST, lceil, unary_convert) DEF_INTERNAL_FLT_FN (LFLOOR, ECF_CONST, lfloor, unary_convert) DEF_INTERNAL_FLT_FN (LRINT, ECF_CONST, lrint, unary_convert) DEF_INTERNAL_FLT_FN (LROUND, ECF_CONST, lround, unary_convert) DEF_INTERNAL_FLT_FN (LLCEIL, ECF_CONST, lceil, unary_convert) DEF_INTERNAL_FLT_FN (LLFLOOR, ECF_CONST, lfloor, unary_convert) DEF_INTERNAL_FLT_FN (LLRINT, ECF_CONST, lrint, unary_convert) DEF_INTERNAL_FLT_FN (LLROUND, ECF_CONST, lround, unary_convert)=