From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [rfc/rft] [0/3] Remove stabs target macros
Date: Fri, 05 Oct 2007 18:04:00 -0000 [thread overview]
Message-ID: <200710051804.l95I4dO3028442@d12av02.megacenter.de.ibm.com> (raw)
Hello,
the following series of three patches removes (nearly) the last remaining
target macros and TM files. These have to do with special cases of the
stabs debug format on certain platforms:
- VARIABLES_INSIDE_BLOCK
(used on arm configurations)
- STATIC_TRANSFORM_NAME / IS_STATIC_TRANSFORM_NAME
(used on Solaris configurations)
- SOFUN_ADDRESS_MAYBE_MISSING
(used on Solaris configurations and i386/ppc Linux)
I don't know if these special cases are actually still relevant today.
However, the patch series should exactly preserve the current behaviour
on all affected targets, by introducing new gdbarch callbacks instead.
Unfortunately, I'm unable to actually test this as I don't have access
to any platform where those cases are used (or indeed any platform
using stabs as native debug format).
I've tested the series on s390-ibm-linux and s390x-ibm-linux without
regressions (when using DWARF-2). I've also ran the testsuite using
CC="gcc -gstabs+" to enforce use of stabs; there were no regressions
introduced by the patches either (however, test results were generally
bad anyway).
I'd appreciate any comments on those patches, and in particular it
would be great if anyone could test them on one of the affected
platforms.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2007-10-05 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 18:04 Ulrich Weigand [this message]
2007-10-05 21:03 ` Joel Brobecker
2007-10-06 13:23 ` Ulrich Weigand
2007-10-07 7:29 ` Joel Brobecker
2007-10-08 15:47 ` Joel Brobecker
2007-10-08 15:59 ` Ulrich Weigand
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=200710051804.l95I4dO3028442@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@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: 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