From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI/prototype: re-implement relocs on ppc-aix
Date: Mon, 15 Apr 2013 16:05:00 -0000 [thread overview]
Message-ID: <20130415070018.GA3525@adacore.com> (raw)
In-Reply-To: <871uaffoq8.fsf@fleche.redhat.com>
> I just mean taking the current default_symfile_offsets and changing it
> to:
>
> ... default_symfile_offsets_base () { ...
> everything except setting the offsets to defaults
> }
>
> default_symfile_offsets () {
> default_symfile_offsets_base()
> ... set the offsets to the defaults
> }
>
> Then your code can call default_symfile_offsets_base.
Indeed.
> Joel> +static struct obj_section *
> Joel> +data_obj_section_from_objfile (struct objfile *objfile)
> Joel> +{
> Joel> + struct obj_section *osect;
> Joel> +
> Joel> + ALL_OBJFILE_OSECTIONS (objfile, osect)
> Joel> + if (strcmp (bfd_section_name (objfile->obfd,
> Joel> osect->the_bfd_section),
> Joel> + ".data") == 0)
> Joel> + return osect;
>
> Tom> Can this not look at objfile->data_sect_index?
>
> Joel> Not if I am understanding it right. objfile->sect_index_data is
> Joel> an index in the objfile->section_offsets array. I couldn't convince
> Joel> myself from the current documentation that those indices applied
> Joel> to both objfile->section_offsets and objfile->sections. It would be
> Joel> ideal if I could!
>
> After the obj_section merge, they are the same.
... and it looks like the patch series is in, too. I will make that
change too. Since the change is not in 7.6, and I'd like my patch
to be reasonably applicable to that branch, I'll keep that part as
a second patch.
--
Joel
prev parent reply other threads:[~2013-04-15 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 23:59 Joel Brobecker
2013-03-22 20:43 ` Tom Tromey
2013-03-26 3:12 ` Joel Brobecker
2013-04-15 12:50 ` Tom Tromey
2013-04-15 16:05 ` Joel Brobecker [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=20130415070018.GA3525@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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