From: Ian Lance Taylor <ian@cygnus.com>
To: bowman@waterloo.hp.com
Cc: gas2@cygnus.com
Subject: Re: elf32-mips, objcopy, reginfo
Date: Mon, 29 Apr 1996 14:35:00 -0000 [thread overview]
Message-ID: <199604292135.RAA00703@sanguine.cygnus.com> (raw)
In-Reply-To: <199604292124.AA117383073@hppadap.waterloo.hp.com>
From: Don Bowman <bowman@waterloo.hp.com>
Date: Mon, 29 Apr 96 17:24:33 EDT
I've found a problem in objcopy/bfd 960425.
If I do a simple objcopy infile outfile,
the ri_gp_value register in the .reginfo section is set to 0.
This occurs since:
1) The input section is copied to the output section
2) mips_elf_section_processing subsequently copies elf_gp there,
but elf_gp was never set for an objcopy.
Does anyone have any suggestions on the best place to change this?
It seems that all of the processing except mips_elf_section_processing
is architecture independent. The bfd_map_over_sections on both
setup_section and copy_section doesn't set the output elf_gp
to the input_gp ever.
At the time I do the mips_elf_section_processing, I no longer
have the input bfd.
Advice?
This type of thing should normally be handled in the copy_private_data
routine: mips_elf_copy_private_bfd_data.
Ian
prev parent reply other threads:[~1996-04-29 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-29 14:24 Don Bowman
1996-04-29 14:35 ` Ian Lance Taylor [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=199604292135.RAA00703@sanguine.cygnus.com \
--to=ian@cygnus.com \
--cc=bowman@waterloo.hp.com \
--cc=gas2@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).