From: "Steve Ellcey " <sellcey@mips.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [patch, mips, stabs] Do any MIPS targets use stabs?
Date: Mon, 07 Jan 2013 18:27:00 -0000 [thread overview]
Message-ID: <99d6779b-5dee-4fac-bc73-26055eaa0857@EXCHHUB01.MIPS.com> (raw)
While testing all the variations of my mips-mti-elf target I found that
a number of debug tests like gcc.dg/debug/trivial.c fail when compiled
using a stabs debug flag (-gstabs3 for example) and -mips16. While running
the GNU simulator I get:
mips-core: 1 byte read to unmapped address 0xffffe820 at 0xffffffff80020278
program stopped with signal 10 (User defined signal 1).
FAIL: gcc.dg/debug/trivial.c -gstabs3 -O execution test
Since I don't actually care about STABS I was looking at undefining
DBX_DEBUGGING_INFO in mips-mti-elf.h and mips-mti-linux.h which makes
the failures a moot point for me since I would no longer run the tests
with any -stabs flags.
But I was wondering, are there any MIPS targets that do use stabs? If not
maybe we should just remove the define of DBX_DEBUGGING_INFO from mips.h
instead of undefing it just for my targets. Opinions?
I saw the discussion about removing STABS completely from GCC, etc. but it
looks like there is still some users who want it on some targets.
Here is my default patch which just undef's it for the mti targets.
Steve Ellcey
sellcey@mips.com
2013-01-07 Steve Ellcey <sellcey@mips.com>
* config/mips/mips-mti-elf.h: undef DBX_DEBUGGING_INFO.
* config/mips/mips-mti-linux.h: Ditto.
diff --git a/gcc/config/mips/mti-elf.h b/gcc/config/mips/mti-elf.h
index f6b38a5..f90b060 100644
--- a/gcc/config/mips/mti-elf.h
+++ b/gcc/config/mips/mti-elf.h
@@ -41,3 +41,6 @@ along with GCC; see the file COPYING3. If not see
\
/* Configuration-independent MIPS rules. */ \
BASE_DRIVER_SELF_SPECS
+
+
+#undef DBX_DEBUGGING_INFO
diff --git a/gcc/config/mips/mti-linux.h b/gcc/config/mips/mti-linux.h
index cda9bdc..c12138f 100644
--- a/gcc/config/mips/mti-linux.h
+++ b/gcc/config/mips/mti-linux.h
@@ -45,3 +45,5 @@ along with GCC; see the file COPYING3. If not see
\
/* Use the standard linux specs for everything else. */ \
LINUX64_DRIVER_SELF_SPECS
+
+#undef DBX_DEBUGGING_INFO
next reply other threads:[~2013-01-07 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:27 Steve Ellcey [this message]
2013-01-07 20:30 ` Richard Sandiford
2013-01-07 20:38 ` Richard Sandiford
2013-01-07 20:54 ` Steve Ellcey
2013-01-08 16:30 ` Steve Ellcey
2013-01-07 20:41 ` Steve Ellcey
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=99d6779b-5dee-4fac-bc73-26055eaa0857@EXCHHUB01.MIPS.com \
--to=sellcey@mips.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).