public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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: Tue, 09 Jan 2024 11:04:03 +0000 [thread overview] Message-ID: <bug-113284-4-WIdcX1W1KB@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 #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Ilya Leoshkevich from comment #4) > Thanks, I can repro this on cfarm203 now. Apparently I missed > > diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc > index 94fbf46f2b6..fd9bb807957 100644 > --- a/gcc/config/rs6000/rs6000.cc > +++ b/gcc/config/rs6000/rs6000.cc > @@ -21334,7 +21334,7 @@ rs6000_elf_declare_function_name (FILE *file, const > char *name, tree decl) > if (TARGET_64BIT && DEFAULT_ABI != ABI_ELFv2) > { > fputs ("\t.section\t\".opd\",\"aw\"\n\t.align 3\n", file); > - ASM_OUTPUT_LABEL (file, name); > + ASM_OUTPUT_FUNCTION_LABEL (file, name, decl); Is that correct? The function label is emitted in the .opd section on powerpc big endian, but I think we want the .LASAN label to be in the text section instead, e.g. after the rs6000_output_function_entry (file, name); label emitted a few lines later. > fputs (DOUBLE_INT_ASM_OP, file); > rs6000_output_function_entry (file, name); > fputs (",.TOC.@tocbase,0\n\t.previous\n", file); > > in commit c659dd8bfb55 ("Implement ASM_DECLARE_FUNCTION_NAME using > ASM_OUTPUT_FUNCTION_LABEL"). I will start a full regtest and send a patch > shortly. Before your changes, we used to emit something like .section ".opd","aw" .align 3 foo: .quad .L.foo,.TOC.@tocbase,0 .previous .type foo, @function .L.foo: .LASANPC0: .LFB0: .cfi_startproc The above patch would emit the .LASANPC0: label after foo:, which is clearly incorrect, it really should go where it was emitted before. Completely untested: --- gcc/config/rs6000/rs6000.cc.jj 2024-01-05 15:22:21.915684074 +0100 +++ gcc/config/rs6000/rs6000.cc 2024-01-09 12:03:09.295509894 +0100 @@ -21357,6 +21357,10 @@ rs6000_elf_declare_function_name (FILE * ASM_DECLARE_RESULT (file, DECL_RESULT (decl)); rs6000_output_function_entry (file, name); fputs (":\n", file); + if ((flag_sanitize & SANITIZE_ADDRESS) + && (in_cold_section_p == first_function_block_is_cold) + && cfun) + asan_function_start (); return; }
next prev parent reply other threads:[~2024-01-09 11:04 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 [this message] 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 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-WIdcX1W1KB@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: linkBe 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).