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 sanitizer/113284] [14 regression] many failures in asan after r14-6946-ge66dc37b299cac
Date: Fri, 12 Jan 2024 09:52:36 +0000	[thread overview]
Message-ID: <bug-113284-4-FW7ZVxCXg1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113284-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Ilya Leoshkevich <iii@gcc.gnu.org>:

https://gcc.gnu.org/g:d8c1361220ba7617adf4ccc396499f6393ec223e

commit r14-7176-gd8c1361220ba7617adf4ccc396499f6393ec223e
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date:   Tue Jan 9 11:40:14 2024 +0100

    rs6000: Fix ASAN linker errors for Power ELF V1 ABI [PR113284]

    rs6000_elf_declare_function_name () outputs Power ELF V1 ABI function
    entry labels without using ASM_OUTPUT_FUNCTION_LABEL ().  As a result,
    .LASANPC labels are not emitted, causing linker errors.

    In theory, it is possible to reuse ASM_OUTPUT_FUNCTION_LABEL () by
    changing rs6000_output_function_entry () to generate label names
    without outputting them, but this would be quite a large change.

    Instead, factor out the .LASANPC emitting code from
    ASM_OUTPUT_FUNCTION_LABEL () and call it manually.

    Fixes: c659dd8bfb55 ("Implement ASM_DECLARE_FUNCTION_NAME using
ASM_OUTPUT_FUNCTION_LABEL")
    Suggested-by: Jakub Jelinek <jakub@redhat.com>
    Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>

    gcc/ChangeLog:

            PR sanitizer/113284
            * config/rs6000/rs6000.cc (rs6000_elf_declare_function_name):
            Use assemble_function_label_final () for Power ELF V1 ABI.
            * output.h (assemble_function_label_final): New function.
            * varasm.cc (assemble_function_label_raw): Use
            assemble_function_label_final ().
            (assemble_function_label_final): New function.

  parent reply	other threads:[~2024-01-12  9:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 22:13 [Bug sanitizer/113284] New: " seurer at gcc dot gnu.org
2024-01-08 22:26 ` [Bug sanitizer/113284] " iii at linux dot ibm.com
2024-01-08 22:30 ` pinskia at gcc dot gnu.org
2024-01-08 23:54 ` seurer at gcc dot gnu.org
2024-01-09  8:32 ` rguenth at gcc dot gnu.org
2024-01-09 10:39 ` iii at linux dot ibm.com
2024-01-09 11:04 ` jakub at gcc dot gnu.org
2024-01-09 13:58 ` iii at linux dot ibm.com
2024-01-09 14:06 ` jakub at gcc dot gnu.org
2024-01-12  9:52 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-27  3:59 ` bergner at gcc dot gnu.org
2024-03-07 20:52 ` law at gcc dot gnu.org
2024-03-08 21:31 ` seurer 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-113284-4-FW7ZVxCXg1@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).