public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/29247] [gdb, tdep] ../../gdb/ppc-sysv-tdep.c:1945: internal-error: ppc64_sysv_abi_return_value: Assertion `ok' failed Date: Thu, 30 Jun 2022 22:47:29 +0000 [thread overview] Message-ID: <bug-29247-4717-uyYa0r9yEd@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29247-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29247 Carl E Love <cel at us dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #14167|0 |1 is obsolete| | --- Comment #18 from Carl E Love <cel at us dot ibm.com> --- Created attachment 14186 --> https://sourceware.org/bugzilla/attachment.cgi?id=14186&action=edit Add IEEE support for float 128bit, version 3 Yes, the previous patch had { issues. I split the patch into a functional change patch and a debug print patch. Unfortunately, I didn't get it done cleanly as I found out later when I compiled just the functional patch. The latest version merges the IEEE Float 128-bit and vector if clauses where possible. It updates ppc64_elfv2_abi_homogeneous_aggregate to support the IEEE 128-bit floating point. That change fixes the rest of the issues with the gdb.base/infcall-nested-structs-c.exp test. The patch also fixes all of the regression failures for gdb.base/infcall-nested-structs-c++.exp. The current patch fixes 8 of the 9 failures in gdb.base/structs.exp. The test description for the one failing test is: "Implemented by calling the one parameter function "Fun$N" which stores its parameter in the global variable "L$N". GDB then examining that global to confirm that the value is as expected." The test defines the global structures: struct struct1 {tA a;}; struct struct2 {tA a; tB b;}; struct struct3 {tA a; tB b; tC c; }; ... and ... struct struct1 foo1 = {'1'}, L1; struct struct2 foo2 = {'a','2'}, L2; struct struct3 foo3 = {'1','b','3'}, L3; ... void Fun1(struct struct1 foo1) { L1 = foo1; } The gdb test prints the value of L1 as follows: p/c L1 $2 = {a = 0 '\000'} (gdb) FAIL: gdb.base/structs.exp: types=tld: p/c L<n>; call 1 structs-tld The tld indicates that the test is for the long double (IEEE Float 128-bit) case. Note, the test p/c L2 $3 = {a = 97 'a', b = 50 '2'} (gdb) PASS: gdb.base/structs.exp: types=tld: p/c fun<n>(); call 2 structs-tld passes. The print for the global values do not appear to use any of the functions in gdb/ppc-sysv-tdep.c. I have yet to find how gdb handles the global variable case. I haven't seen anything yet in the ABI about it either. Any hints on where the issue is for the global case would be appreciated. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-30 22:47 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-14 8:58 [Bug tdep/29247] New: " vries at gcc dot gnu.org 2022-06-14 14:51 ` [Bug tdep/29247] " vries at gcc dot gnu.org 2022-06-15 11:59 ` vries at gcc dot gnu.org 2022-06-15 13:27 ` vries at gcc dot gnu.org 2022-06-15 14:47 ` vries at gcc dot gnu.org 2022-06-15 14:51 ` vries at gcc dot gnu.org 2022-06-15 15:49 ` vries at gcc dot gnu.org 2022-06-15 15:59 ` vries at gcc dot gnu.org 2022-06-15 22:47 ` vries at gcc dot gnu.org 2022-06-16 13:53 ` jamborm at gcc dot gnu.org 2022-06-20 12:25 ` ulrich.weigand at de dot ibm.com 2022-06-21 16:32 ` cel at us dot ibm.com 2022-06-23 15:19 ` cel at us dot ibm.com 2022-06-23 15:22 ` cel at us dot ibm.com 2022-06-23 15:30 ` ulrich.weigand at de dot ibm.com 2022-06-23 19:56 ` cel at us dot ibm.com 2022-06-24 0:53 ` cel at us dot ibm.com 2022-06-24 11:53 ` ulrich.weigand at de dot ibm.com 2022-06-25 0:42 ` cel at us dot ibm.com 2022-06-25 2:51 ` ulrich.weigand at de dot ibm.com 2022-06-30 22:47 ` cel at us dot ibm.com [this message] 2022-07-12 9:15 ` ulrich.weigand at de dot ibm.com 2022-07-13 17:46 ` cel at us dot ibm.com 2022-07-15 15:32 ` cel at us dot ibm.com 2022-07-15 16:09 ` cel at us dot ibm.com 2022-07-27 8:45 ` vries at gcc dot gnu.org 2022-07-27 15:38 ` cel at us dot ibm.com 2022-07-27 15:42 ` vries at gcc dot gnu.org 2022-07-27 16:54 ` cel at us dot ibm.com 2022-09-02 12:55 ` vries at gcc dot gnu.org 2022-09-02 13:09 ` vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29247-4717-uyYa0r9yEd@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).