public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/104633] [12 Regression] -Winfinite-recursion diagnoses fortify wrappers
Date: Tue, 22 Feb 2022 10:50:30 +0000	[thread overview]
Message-ID: <bug-104633-4-0o8sgKDu2I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104633-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
The following is a valid use of extern inline I think

extern int memcmp (const void * p, const void *q, unsigned long size);

extern inline __attribute__((always_inline,gnu_inline))
int memcmp (const void * p, const void *q, unsigned long size)
{
  return memcmp (p, q, size);
}

int foo (const void * p, const void *q)
{
  return memcmp (p, q, 4);
}

I think the user needs to avoid name-lookup issues here by using an alias
for the call to memcmp in the inline wrapper which might also avoid the
diagnostic.  That __builtin_memcmp finds the memcmp definition is quite
unfortunate and makes it not usable as a way to avoid using an alias.

  parent reply	other threads:[~2022-02-22 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  8:55 [Bug c/104633] New: " rguenth at gcc dot gnu.org
2022-02-22  8:56 ` [Bug c/104633] " rguenth at gcc dot gnu.org
2022-02-22 10:02 ` rguenth at gcc dot gnu.org
2022-02-22 10:50 ` rguenth at gcc dot gnu.org [this message]
2022-02-22 11:16 ` jakub at gcc dot gnu.org
2022-02-22 12:35 ` jakub at gcc dot gnu.org
2022-02-23  4:04 ` egallager at gcc dot gnu.org
2022-02-23 11:04 ` cvs-commit at gcc dot gnu.org
2022-02-23 11:50 ` 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-104633-4-0o8sgKDu2I@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).