From: Sachin Monga via Gdb <gdb@sourceware.org>
To: Sachin Monga <sachin.monga82@gmail.com>,
Peter Bergner <bergner@tenstorrent.com>
Cc: Michael Meissner <meissner@linux.ibm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Adhemerval Zanella Netto via Gdb <gdb@sourceware.org>,
libc-help@sourceware.org, Tom Tromey <tom@tromey.com>,
Surya Kumari Jangala <jskumari@linux.ibm.com>,
Carl Love <cel@us.ibm.com>
Subject: Re: [EXT] Re: gdb does not stop at printf for ppc
Date: Wed, 5 Nov 2025 11:30:41 +0530 [thread overview]
Message-ID: <077e417f-f82f-46ad-9cae-3cd10d6dbf13@linux.ibm.com> (raw)
In-Reply-To: <CALfcnBoLGEd4umNX-X6q+9V6rz4KgXNRMMntNrAPVbbYpiv5Fg@mail.gmail.com>
Hi Peter/All
>diff --git a/sysdeps/ieee754/ldbl-128ibm-compat/ieee128-printf.c
b/sysdeps/ieee754/ldbl-128ibm-compat/ieee128-printf.c
>index 7b1640ceac..d567d98c68 100644
>--- a/sysdeps/ieee754/ldbl-128ibm-compat/ieee128-printf.c
>+++ b/sysdeps/ieee754/ldbl-128ibm-compat/ieee128-printf.c
>@@ -33,3 +33,6 @@ ___ieee128_printf (const char *format, ...)
> return done;
>}
>strong_alias (___ieee128_printf, __printfieee128)
>+
>+asm (".local printf\n"
>+ ".set printf, __printfieee128");
> ZjQcmQRYFpfptBannerEnd
> Thanks Adhemerval/Peter
>
> Ok, I can try for the printf and test it.
I've tested the solution provided by Adhmerval and it worked well. No
regressions found on test-suite also.
Also, it rules out the ieee ABI machine logic since
"-mabi=ieeelongdouble" does not seem to have impact over the reported issue.
Next, my question to the community is that do I need to create aliasing
for all the symbols as in the list prepared by Carl as discussed in the
thread ?
For now, I need urgent solution for printf specifically. So, Is it ok to
proceed and share this change for printf only ?
Regards:
Sachin.
next prev parent reply other threads:[~2025-11-05 6:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f4e905f7-48cb-439a-a8e6-a50242c18e6a@linux.ibm.com>
2025-10-01 4:03 ` Peter Bergner via Gdb
2025-10-01 17:20 ` Adhemerval Zanella Netto via Gdb
2025-10-02 15:57 ` [EXT] " Peter Bergner via Gdb
2025-10-02 16:19 ` Carl Love via Gdb
2025-10-02 16:58 ` Florian Weimer via Gdb
2025-10-02 18:12 ` Peter Bergner via Gdb
2025-10-02 18:49 ` Billie Alsup (balsup) via Gdb
2025-10-02 19:09 ` Peter Bergner via Gdb
2025-10-03 19:43 ` Tom Tromey
2025-10-07 17:21 ` Adhemerval Zanella Netto via Gdb
2025-10-15 14:33 ` [EXT] " Peter Bergner via Gdb
2025-10-15 17:09 ` Sachin Monga via Gdb
2025-11-05 6:00 ` Sachin Monga via Gdb [this message]
2025-11-06 4:13 ` Peter Bergner via Gdb
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=077e417f-f82f-46ad-9cae-3cd10d6dbf13@linux.ibm.com \
--to=gdb@sourceware.org \
--cc=bergner@tenstorrent.com \
--cc=cel@us.ibm.com \
--cc=jskumari@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-help@sourceware.org \
--cc=meissner@linux.ibm.com \
--cc=sachin.monga82@gmail.com \
--cc=segher@kernel.crashing.org \
--cc=smonga@linux.ibm.com \
--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