public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110729] -fpatchable-function-entries: __patchable_function_entries has wrong sh_link
Date: Fri, 21 Jul 2023 05:18:55 +0000	[thread overview]
Message-ID: <bug-110729-4-TUweZY3LK2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110729-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110729

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:6894581ac453361e3fb4e1ffd54f9499acb87466

commit r14-2693-g6894581ac453361e3fb4e1ffd54f9499acb87466
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Fri Jul 21 00:16:29 2023 -0500

    testsuite: Add a test case for PR110729 [PR110729]

    As PR110729 reported, there was one issue for .section
    __patchable_function_entries with -ffunction-sections, that
    is we put the same symbol as link_to section symbol for all
    functions wrongly.  The commit r13-4294 for PR99889 has
    fixed this with the corresponding label LPFE* which sits in
    the function_section.

    As Fangrui suggested [1], this patch is to add a bit more
    test coverage.  I didn't find a good way to check all
    linked_to symbols are different, so I checked for LPFE[012].

    [1] https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624866.html

            PR testsuite/110729

    gcc/testsuite/ChangeLog:

            * gcc.dg/pr110729.c: New test.

  parent reply	other threads:[~2023-07-21  5:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  6:20 [Bug middle-end/110729] New: " i at maskray dot me
2023-07-19  6:24 ` [Bug middle-end/110729] " pinskia at gcc dot gnu.org
2023-07-19  6:26 ` pinskia at gcc dot gnu.org
2023-07-19  6:27 ` pinskia at gcc dot gnu.org
2023-07-19  6:28 ` pinskia at gcc dot gnu.org
2023-07-21  5:18 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-21  5:49 ` linkw at gcc dot gnu.org

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=bug-110729-4-TUweZY3LK2@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).