public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"tom@tromey.com" <tom@tromey.com>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>,
	Sanket Rathi <sanrathi@in.ibm.com>,
	"simark@simark.ca" <simark@simark.ca>
Subject: Re: [PATCH] Fix call functions command bug in 64-bit programs for AIX
Date: Thu, 24 Nov 2022 17:56:14 +0000	[thread overview]
Message-ID: <CH2PR15MB354479B2992BD63534B2522FD60F9@CH2PR15MB3544.namprd15.prod.outlook.com> (raw)
In-Reply-To: <48b9cc7b5cb4981f03fd459c4365242a11546c1e.camel@de.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 3580 bytes --]

Hi Ulrich,

Thank you for pushing the patch. Sure..

Hi Tom,

>> warning: (Internal error: pc 0x10000290 in read in psymtab, but not in symtab.)

>This normally indicates a serious bug.  Also, I guess you must be using
>stabs?

>> BFD: /usr/lib/libc.a(/usr/lib/libc.a(shr_64.o)): wrong auxtype 0xff for storage class 0x2
>> BFD: /usr/lib/libc.a(/usr/lib/libc.a(shr_64.o)): wrong auxtype 0xff for storage class 0x6b

>These seem concerning.

I will check why this is happening. I will plan for it in our future patches for AIX and keep you in cc in that mailing thread once I find a solution. By the way I use DWARF for all the tests I do.


>I didn't look at this too deeply, but it's worth noting that code
>handling the marshalling of integers should also handle
>TYPE_CODE_FIXED_POINT as well, as those are integers with a funny
>name.  There should be some Ada tests for this.

>If you can't test Ada, I guess don't worry about it.  I'm not 100% sure
>the way you've written this will work for a fixed-point number.

So, I had been searching for TYPE_CODE_FIXED_POINT. Unfortunately, when I tried running the Ada test cases for the same,  the output was that the test case is unsupported.

One of the things about fixed point numbers is I have not found a way I can write the same in C or C++ in AIX. For example, I found how IBM Z folks do it which is in the link [ https://www.ibm.com/docs/en/zos/2.4.0?topic=specifiers-fixed-point-decimal-types-c-only#dcon ]. While few of other platforms that do not have float type use this [ https://www.ibm.com/docs/en/rhapsody/8.4.0?topic=elements-using-fixed-point-variables ].

Kindly let me know if any of you know how we can use it in C/C++ in AIX. I would like to learn and then check how we can handle them in GDB. So far in C or C++ I have not been successful in finding how to use fixed point integers in AIX.

Have a nice day ahead.

Thanks and regards,
Aditya.

Using fixed-point variables<https://www.ibm.com/docs/en/rhapsody/8.4.0?topic=elements-using-fixed-point-variables>
You can use IBM Rational Rhapsody Developer for C to provide an option to use fixed-point variables for target systems that do not include floating-point capabilities.
www.ibm.com

Fixed point decimal types (C only) - IBM<https://www.ibm.com/docs/en/zos/2.4.0?topic=specifiers-fixed-point-decimal-types-c-only#dcon>
Fixed point decimal types are classified as arithmetic types. To declare fixed point decimal variables and initialize them with fixed point decimal constants, you use the type specifier decimal.For this type specifier, decimal is a macro that is defined in the decimal.h header file. Remember to include decimal.h if you use fixed point decimals in your program.
www.ibm.com



________________________________
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Sent: 17 November 2022 18:24
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>; Aditya Kamath1 <Aditya.Kamath1@ibm.com>; simon.marchi@efficios.com <simon.marchi@efficios.com>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>; tom@tromey.com <tom@tromey.com>; Sanket Rathi <sanrathi@in.ibm.com>
Subject: Re: [PATCH] Fix call functions command bug in 64-bit programs for AIX

Aditya Kamath1 <Aditya.Kamath1@ibm.com> wrote:

>You were right. Thank you for pointing out. I have attached
>the outputs below. It works fine now.

This version is OK, I've checked it in now.

Tom does make very valid points in his reply however,
so it would be good if you can still follow up on that.

Bye,
Ulrich


  reply	other threads:[~2022-11-24 17:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 11:00 Aditya Kamath1
2022-11-08 13:30 ` Ulrich Weigand
2022-11-11 17:53   ` Aditya Kamath1
2022-11-14 15:54     ` Ulrich Weigand
2022-11-14 17:32       ` Aditya Kamath1
2022-11-14 18:19         ` Ulrich Weigand
2022-11-14 18:28           ` Aditya Kamath1
2022-11-14 18:43             ` Ulrich Weigand
2022-11-14 18:52               ` Aditya Kamath1
2022-11-14 19:10                 ` Ulrich Weigand
2022-11-16 11:27                   ` Aditya Kamath1
2022-11-16 15:15                     ` Ulrich Weigand
2022-11-16 18:07                       ` Aditya Kamath1
2022-11-16 18:30                         ` Tom Tromey
2022-11-17 12:54                         ` Ulrich Weigand
2022-11-24 17:56                           ` Aditya Kamath1 [this message]
2022-11-24 18:15                             ` Tom Tromey
2023-04-14  7:38                               ` [PATCH] Fix call functions command bug in 64-bit programs for AIX and PC read in psymtab-symtab warning Aditya Kamath1
2023-04-14 14:45                                 ` Tom Tromey
2023-04-17 13:08                                   ` Aditya Kamath1
2023-04-17 13:16                                     ` Aditya Kamath1
2023-04-18 10:12                                       ` Ulrich Weigand
2023-04-21 13:00                                         ` Aditya Kamath1
2023-04-24 15:44                                           ` Ulrich Weigand
2023-04-27 10:13                                             ` Aditya Kamath1
2023-04-27 12:23                                               ` Ulrich Weigand
2023-04-27 10:14                                   ` Aditya Kamath1

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=CH2PR15MB354479B2992BD63534B2522FD60F9@CH2PR15MB3544.namprd15.prod.outlook.com \
    --to=aditya.kamath1@ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sangamesh.swamy@in.ibm.com \
    --cc=sanrathi@in.ibm.com \
    --cc=simark@simark.ca \
    --cc=tom@tromey.com \
    /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: link
Be 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).