public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Alex Coplan <alex.coplan@arm.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] gas: Fix internal error in S_SET_SEGMENT
Date: Wed, 22 Jul 2020 07:40:08 -0700	[thread overview]
Message-ID: <CAMe9rOpfWfpENKmmzZ-51z7dc21O57miQT89e+SHcfHhd7d5Ow@mail.gmail.com> (raw)
In-Reply-To: <20200722142302.wi2rotbr3hbz57iw@arm.com>

On Wed, Jul 22, 2020 at 7:24 AM Alex Coplan <alex.coplan@arm.com> wrote:
>
> Hello,
>
> This patch fixes an internal error in GAS when defining a section using
> a symbol that has already been named but not defined. For a minimal
> reproducer, try the following input:
>
> a=b
> .sect a
>
> The problem is that obj_elf_change_section() happily reuses the symbol
> "a" created by equals() without clearing the sy_value field: prior to
> this patch, it just set bsym. This caused a problem when attempting to
> resolve the section symbol, since resolve_symbol_value() ended up
> resolving the symbol as if it were the original symbol created by
> equals(), which ends up leaving the section symbol in the undefined
> section instead of in section a, hence the call to abort() in
> S_SET_SEGMENT().
>
> Testing:
>  * New test fails before and passes after the change.
>  * Regression tested on a wide variety of targets.
>
> OK for master?
>
> Thanks,
> Alex
>
> ---
>
> gas/ChangeLog:
>
> 2020-07-22  Alex Coplan  <alex.coplan@arm.com>
>
>         * config/obj-elf.c (obj_elf_change_section): When
>         repurposing an existing symbol, ensure that we set sy_value as
>         per other (fresh) section symbols.
>         * testsuite/gas/aarch64/section-symbol-redef.d: New test.
>         * testsuite/gas/aarch64/section-symbol-redef.s: Input for test.
>

Why are tests arm specific?  Can you put them to ELF tests?

-- 
H.J.

  reply	other threads:[~2020-07-22 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 14:23 Alex Coplan
2020-07-22 14:40 ` H.J. Lu [this message]
2020-08-03 14:22   ` Alex Coplan
2020-08-17  9:07     ` Alex Coplan
2020-08-17 11:26       ` Nick Clifton
2020-08-17 13:28         ` Alex Coplan
2020-09-01 15:47           ` Alex Coplan
2020-09-01 23:44             ` Alan Modra

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=CAMe9rOpfWfpENKmmzZ-51z7dc21O57miQT89e+SHcfHhd7d5Ow@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=alex.coplan@arm.com \
    --cc=binutils@sourceware.org \
    /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).