public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113182] [14 Regression] FAIL: g++.dg/cpp0x/udlit-namespace.C -std=c++14 execution test Date: Sat, 30 Dec 2023 19:26:29 +0000 [thread overview] Message-ID: <bug-113182-4-Nk9zS0lnTp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113182-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113182 --- Comment #4 from John David Anglin <danglin at gcc dot gnu.org> --- Created attachment 56967 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56967&action=edit Assembler output There are no .type directives for _U_* libfuncs. They are emitted by ASM_OUTPUT_EXTERNAL_LIBCALL: /* We need set the type for external libcalls. Also note that not all libcall names are passed to targetm.encode_section_info (e.g., __main). Thus, we also have to do the section encoding if it hasn't been done already. */ #undef ASM_OUTPUT_EXTERNAL_LIBCALL #define ASM_OUTPUT_EXTERNAL_LIBCALL(FILE, FUN) \ do { \ if (!FUNCTION_NAME_P (XSTR (FUN, 0))) \ pa_encode_label (FUN); \ ASM_OUTPUT_TYPE_DIRECTIVE (FILE, XSTR (FUN, 0), "function"); \ } while (0) The .type directives that are emitted are now at the end: .section .debug_str,"",@progbits .ident "GCC: (GNU) 14.0.0 20231128 (experimental) [remotes/origin/trunk r14-6831-ged60b2868ab]" .type tanh, @function
next prev parent reply other threads:[~2023-12-30 19:26 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-30 18:03 [Bug other/113182] New: " danglin at gcc dot gnu.org 2023-12-30 18:30 ` [Bug middle-end/113182] " pinskia at gcc dot gnu.org 2023-12-30 18:38 ` dave.anglin at bell dot net 2023-12-30 19:19 ` danglin at gcc dot gnu.org 2023-12-30 19:26 ` danglin at gcc dot gnu.org [this message] 2024-01-01 20:41 ` danglin at gcc dot gnu.org 2024-01-08 14:19 ` rguenth at gcc dot gnu.org 2024-01-08 14:29 ` jakub at gcc dot gnu.org 2024-01-08 15:56 ` dave.anglin at bell dot net 2024-01-09 18:00 ` jakub at gcc dot gnu.org 2024-01-09 19:56 ` dave.anglin at bell dot net 2024-01-09 20:03 ` dave.anglin at bell dot net 2024-01-10 13:57 ` dave.anglin at bell dot net 2024-01-10 17:49 ` danglin at gcc dot gnu.org 2024-01-11 16:55 ` danglin at gcc dot gnu.org 2024-01-11 17:37 ` jakub at gcc dot gnu.org 2024-01-11 17:47 ` jakub at gcc dot gnu.org 2024-01-11 18:03 ` dave.anglin at bell dot net 2024-01-11 18:25 ` jakub at gcc dot gnu.org 2024-01-11 18:56 ` dave.anglin at bell dot net 2024-01-11 19:05 ` jakub at gcc dot gnu.org 2024-01-11 19:21 ` dave.anglin at bell dot net 2024-01-12 12:59 ` cvs-commit at gcc dot gnu.org 2024-01-12 13:06 ` jakub 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-113182-4-Nk9zS0lnTp@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).