From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 44DFC3858407; Fri, 2 Sep 2022 13:26:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 44DFC3858407 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1662125174; bh=AiG07CHqO4i51nbbz9gqiK9dlMRsEq8xtBc/P6t/fMQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OC2ctdSyPD1J6azckPIP0oohd040vDXfaRemaWV/+P4iAvbvjuBsUdQKY/nCQjUYo gRcMt5zOvPXFmJpnXol4jZ1+lT0NotBVyFbT26hMUtJeCHysKvB23ugr407zY5jBAe +YlVTOm29t+Rv1eYv1jWpVvLOTIGBkKmxbbESjfM= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/29543] [gdb/tdep, ppc] inferior call with long double vararg not handled correctly Date: Fri, 02 Sep 2022 13:26:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29543 Tom de Vries changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[gdb/tdep, ppc] inferior |[gdb/tdep, ppc] inferior |call with complex long |call with long double |double vararg not handled |vararg not handled |correctly |correctly --- Comment #3 from Tom de Vries --- I simplified the example to strip the _Complex, and I still got the same problem, so it's really related to "long double". --=20 You are receiving this mail because: You are on the CC list for the bug.=