From: Peter Bergner via Gdb <gdb@sourceware.org>
To: Sachin Monga <smonga@linux.ibm.com>,
Sachin Monga <sachin.monga82@gmail.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: Re: gdb does not stop at printf for ppc
Date: Wed, 5 Nov 2025 22:13:01 -0600 [thread overview]
Message-ID: <d9c1c89a-a1e7-4536-8259-2c6deba9ef70@oss.tenstorrent.com> (raw)
In-Reply-To: <077e417f-f82f-46ad-9cae-3cd10d6dbf13@linux.ibm.com>
On 11/4/25 10:00 PM, Sachin Monga wrote:
> I've tested the solution provided by Adhmerval and it worked well.
> No regressions found on test-suite also.
Excellent!
> 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 ?
I think it's fine to submit a patch for printf now and wait on the other
symbols later. As Adhemerval mentioned, there are more symbols than just
the IEEE128 symbols that need fixing too, so this looks like it'll be a
multi-patch process to fix everything and I don't expect you to fix the
non-IEEE128 symbols.
That said, I think when fixing printf, we should fix the other printf like
functions at the same time, since they're related. For example, fprintf,
etc. There shouldn't be too many of those.
Peter
prev parent reply other threads:[~2025-11-06 4:15 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
2025-11-06 4:13 ` Peter Bergner via Gdb [this message]
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=d9c1c89a-a1e7-4536-8259-2c6deba9ef70@oss.tenstorrent.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