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 bootstrap/97858] [11 regression] Bogus warnings about va_list during profiledbootstrap Date: Mon, 16 Nov 2020 23:28:09 +0000 [thread overview] Message-ID: <bug-97858-4-BkEBbwwxu3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97858 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |nathan at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Why would be the mkdeps.c ever performance critical? But also, the function is only called with 1 (+ one defaulted to NULL) or 3 (last one NULL) arguments, so can't it be just changed to static const char * munge (const char *str, const char *tail = NULL) and not use any varargs? I don't see any changes to the calls to munge in the modules patchset. Or are there any short term plans to use it with more arguments?
next prev parent reply other threads:[~2020-11-16 23:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-16 18:39 [Bug middle-end/97858] New: " hubicka at gcc dot gnu.org 2020-11-16 22:07 ` [Bug bootstrap/97858] " hubicka at gcc dot gnu.org 2020-11-16 23:28 ` jakub at gcc dot gnu.org [this message] 2020-11-17 7:14 ` rguenth at gcc dot gnu.org 2020-11-17 12:50 ` nathan at gcc dot gnu.org 2020-11-17 14:47 ` cvs-commit at gcc dot gnu.org 2020-11-17 14:53 ` nathan at gcc dot gnu.org 2020-11-17 15:18 ` hubicka at ucw dot cz 2020-11-17 15:36 ` jakub at gcc dot gnu.org 2020-11-17 15:44 ` jakub at gcc dot gnu.org 2020-11-17 15:47 ` [Bug middle-end/97858] [11 regression] Bogus warnings about va_list hubicka at gcc dot gnu.org 2020-11-17 15:50 ` hubicka at gcc dot gnu.org 2021-01-14 9:38 ` [Bug middle-end/97858] " rguenth at gcc dot gnu.org 2021-04-09 19:10 ` [Bug middle-end/97858] avoid mentioning va_list internal fields in -Wuninitialized msebor 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-97858-4-BkEBbwwxu3@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).