From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Danny Backx <danny.backx@scarlet.be>
Cc: binutils@sourceware.org
Subject: Re: Binutils on arm : pls advice me how to proceed
Date: Thu, 11 May 2006 06:37:00 -0000 [thread overview]
Message-ID: <44626F93.1010506@portugalmail.pt> (raw)
In-Reply-To: <1147291981.3774.28.camel@dannypc>
Danny Backx wrote:
> I am having problems applying them to the current CVS version. Almost
> all the diffs fail to apply, I've copied an excerpt below. Am I using
> the wrong version ?
>
>
Did you get a warning about the files not being found? If so, check that
you are applying the patch in the correct directory,
or use the -p option. You can always --dry-run before applying the patch.
> I also tried your patch against binutils-2.16.1 - that only produced
> patch failures in one file (tc-arm.c).
>
>
> Danny
>
> On Wed, 2006-05-10 at 11:48 +0100, Nick Clifton wrote:
>
>> Hi Pedro, Hi Danny,
>>
>> Please accept my apologies in taking so long to reply to your emails.
>> I have now had a chance to go over them and the patches that they
>> contained and then seemed quite reasonable to me. I have applied them
>> to my local source tree and checked to see if there were any regressions
>> - there were not.
>>
>> Unfortunately I do not have an arm-wince system at my disposal, so I
>> cannot check that the (slightly revised) versions of the patches that I
>> applied allow working binaries to be created, so please can I ask for
>> your help ?
>>
>> I am attaching a unified patch which I think contains all of the
>> changes that you suggested, along with a little bit of code tidying.
>> Please could you try applying them to a set of binutils sources (from
>> the mainline of the CVS repository) and testing them to see if they
>> produce working binaries ?
>>
>> One thing I am quite worried about is whether partial linking will
>> work. (ie using the "ld -r ...." file to create an object file that is
>> an amalgam of several other object files). I suspect that there might
>> be problems with the -8 bias to branch relocations, but without a test
>> environment I cannot tell for sure.
>>
>> Thanks very much for perserving with your work, and assuming that you
>> can confirm that the patch works, I will be happy to check it in with
>> the ChangeLogs below.
>>
>> Cheers
>> Nick
>>
>> bfd/ChangeLog
>> 2006-05-10 Pedro Alves <pedro_alves@portugalmail.pt>
>>
>> * coff-arm.c (ARM_26D, ARM_32, ARM_RVA_32, ARM_SECTION,
>> ARM_SECREL): Mark WinCE versions of these relocs as partial
>> inplace.
>> (coff_arm_relocate_section): Adjust addend for WinCE.
>>
>> gas/ChangeLog
>> 2006-05-10 Pedro Alves <pedro_alves@portugalmail.pt>
>>
>> * config/tc-arm.c (md_pcrel_from_section): Force a bias for relocs
>> against external symbols for WinCE targets.
>> (md_apply_fix): Likewise.
>>
>> ld/ChangeLog
>> 2006-05-10 Pedro Alves <pedro_alves@portugalmail.pt>
>>
>> * pe-dll.c (autofilter_symbollist): Add Dllmain,
>> DllMainCRTStartup, _DllMainCRTStartup and .text.
>> (autofilter_liblist): Add libcegcc.
>> (autofilter_symbolprefixlist): Add __imp_ and .idata$.
>> (generate_reloc): Do not skip sections without a SEC_LOAD flag,
>> they can still contain relocs that need processing.
>> Skip the .idata$6 section.
>> (jmp_arm_bytes): New array: Contains byte codes for an ARM jump.
>> (make_one): Use the new array.
>> (make_import_fixup_entry): Use .idata$2 instead of .idata$3.
>> * emultempl/pe.em (MajorSubsystemVersion): Set to 3 for armpe.
>>
>>
>>
next prev parent reply other threads:[~2006-05-10 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 17:55 Danny Backx
2006-05-04 18:03 ` Daniel Jacobowitz
2006-05-04 19:03 ` Pedro Alves
2006-05-05 17:46 ` Nick Clifton
2006-05-10 15:14 ` Nick Clifton
2006-05-11 4:32 ` Danny Backx
2006-05-11 6:37 ` Pedro Alves [this message]
2006-05-11 14:59 ` Nick Clifton
2006-05-11 8:51 ` Pedro Alves
2006-05-11 14:54 ` Nick Clifton
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=44626F93.1010506@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=binutils@sourceware.org \
--cc=danny.backx@scarlet.be \
/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).