From: Richard Sandiford <richard@codesourcery.com>
To: fnf@specifix.com
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFC] Passing MIPS debug hints between gcc and gdb
Date: Mon, 12 Jun 2006 11:07:00 -0000 [thread overview]
Message-ID: <87irn6my72.fsf@talisman.home> (raw)
In-Reply-To: <200606120611.32335.fnf@specifix.com> (Fred Fish's message of "Mon, 12 Jun 2006 06:11:31 -0400")
Fred Fish <fnf@specifix.com> writes:
> 2006-06-12 Fred Fish <fnf@specifix.com>
>
> * config/mips/mips.c (mips_file_start): Create special section
> ".gcc_compiled_longXX" for o64 ABI as well as EABI.
Applied. I tweaked the comment to mention o64 as well, so for the
record, here's what went in.
Richard
Index: config/mips/mips.c
===================================================================
--- config/mips/mips.c (revision 114565)
+++ config/mips/mips.c (working copy)
@@ -5830,8 +5830,9 @@ mips_file_start (void)
/* There is no ELF header flag to distinguish long32 forms of the
EABI from long64 forms. Emit a special section to help tools
- such as GDB. */
- if (mips_abi == ABI_EABI)
+ such as GDB. Do the same for o64, which is sometimes used with
+ -mlong64. */
+ if (mips_abi == ABI_EABI || mips_abi == ABI_O64)
fprintf (asm_out_file, "\t.section .gcc_compiled_long%d\n",
TARGET_LONG64 ? 64 : 32);
next prev parent reply other threads:[~2006-06-12 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 16:05 Fred Fish
2006-05-11 6:57 ` Richard Sandiford
2006-05-11 10:16 ` Fred Fish
2006-05-17 20:32 ` Fred Fish
2006-05-18 0:04 ` Mark Mitchell
2006-05-18 16:53 ` Richard Sandiford
2006-06-12 10:10 ` Fred Fish
2006-06-12 11:07 ` Richard Sandiford [this message]
2006-06-13 16:08 ` Fred Fish
2006-06-13 17:42 ` Daniel Jacobowitz
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=87irn6my72.fsf@talisman.home \
--to=richard@codesourcery.com \
--cc=fnf@specifix.com \
--cc=gcc-patches@gcc.gnu.org \
--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