From: Fred Fish <fnf@specifix.com>
To: Richard Sandiford <richard@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFC] Passing MIPS debug hints between gcc and gdb
Date: Thu, 11 May 2006 10:16:00 -0000 [thread overview]
Message-ID: <200605110617.01171.fnf@specifix.com> (raw)
In-Reply-To: <87y7x9aw12.fsf@talisman.home>
On Thursday 11 May 2006 02:57, Richard Sandiford wrote:
> You're right: the size of everything is determined by the combination of
> the ABI "name" and long size. The gdb patch I mentioned did do that IIRC.
> (I didn't write that patch myself, and my memory's hazy.) It was certainly
> the intention that gdb work this out for itself.
OK. I can generate a patch that does that.
> Using empty sections was always a hack, to be honest (modelled on the
> old .gcc_compiled_v3 thing, whatever it was called). I suppose we
> should be using note sections really.
Yeah, I thought about putting the hints in a single section that could
have it's contents merged by the linker and duplicates removed.
> I'd be OK with relaxing the condition to EABI || o64 if it's o64 you
> need this for.
Yes, it is o64 where I originally found the problem.
> I suppose we should make the incorrect -mlong* option an error for
> other ABIs. (Another one for the TODO list.)
OK, though it seemed to work fine with at least one other ABI (-mabi=32).
I didn't test them all.
-Fred
next prev parent reply other threads:[~2006-05-11 10:16 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 [this message]
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
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=200605110617.01171.fnf@specifix.com \
--to=fnf@specifix.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=richard@codesourcery.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