public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jojo R <rjiejie@linux.alibaba.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: [PATCH v2] Support multiple .eh_frame sections
Date: Thu, 3 Nov 2022 10:11:34 +0800	[thread overview]
Message-ID: <30787b1e-ddd1-6841-17ff-bf75773a20ff@linux.alibaba.com> (raw)
In-Reply-To: <9e232c97-b0c7-763e-bcc6-f998716a35fd@redhat.com>


在 2022/11/2 20:21, Nick Clifton 写道:
> Hi Jojo,
>
>>     This patch is based on MULTIPLE_FRAME_SECTIONS and 
>> EH_FRAME_LINKONCE,
>>     it allows backend to enable this feature and use '--gc-sections' 
>> simply.
>
> Do you (or your employer) have a copyright assignment on file with the 
> FSF for
> contributions to the GNU Binutils project ?  If not, are you willing 
> to contribute
> the patch with a DCO attached ? https://developercertificate.org/
>
Yes, we have signed the assignment of FSF :)
>
>>   _bfd_elf_default_action_discarded (asection *sec)
>>   {
>> +  const struct elf_backend_data *bed;
>> +  bed = get_elf_backend_data (sec->owner);
>> +
>> +  if (bed->elf_backend_can_make_multiple_eh_frame
>> +      && strncmp (sec->name, ".eh_frame.", 10) == 0)
>> +    return 0;
>> +
>>     if (sec->flags & SEC_DEBUGGING)
>>       return PRETEND;
>
> I think that this test would be better if it was moved down a few lines,
> until it was just after this test:
>
>   if (strcmp (".eh_frame", sec->name) == 0)
>     return 0;
>
Fixed.
>
>> +      exp.X_op = O_symbol;
>> +      exp.X_add_symbol = (symbolS *) local_symbol_make (cseg->name, 
>> cseg, 0, frch->frch_root);;
>> +      exp.X_add_number = 0;
>
> The arguments to local_symbol_make() are in the wrong order:
>
>   struct local_symbol *local_symbol_make (const char *, segT, fragS *, 
> valueT);
>
> Ie the frag should come before the value.
>
> Also there is a double semi-colon at the end of the line.
Fixed.
>
> Cheers
>   Nick

  reply	other threads:[~2022-11-03  2:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  7:48 [PATCH] " Jojo R
2022-08-01 11:10 ` Nick Clifton
2022-08-02  7:23   ` Jojo R
2022-11-02  8:01 ` [PATCH v2] " Jojo R
2022-11-02 12:21   ` Nick Clifton
2022-11-03  2:11     ` Jojo R [this message]
2022-11-03  2:04   ` [PATCH v3] " Jojo R
2022-11-03 10:26     ` Nick Clifton
2022-11-03 19:34       ` Fangrui Song
     [not found]       ` <DS7PR12MB57653A2E86C6779B24889E51CB389@DS7PR12MB5765.namprd12.prod.outlook.com>
2022-11-04  1:50         ` Jojo R

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=30787b1e-ddd1-6841-17ff-bf75773a20ff@linux.alibaba.com \
    --to=rjiejie@linux.alibaba.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).