public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29093] clang fails to compile 0.187: error: format string is not a string literal
Date: Tue, 26 Apr 2022 18:04:58 +0000	[thread overview]
Message-ID: <bug-29093-10460-TAq98sHR7T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29093-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29093

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
This is in fallback code in case the platform doesn't have error.h, but does
have err.h.

This seems to be a difference/bug between gcc and clang -Wformat-nonliteral.

Clang implements this mostly the same way as GCC, but there is a difference for
functions that accept a va_list argument (for example, vprintf). GCC does not
emit -Wformat-nonliteral warning for calls to such functions.

You might be able to fix this by annotating the error function itself.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-04-26 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 17:33 [Bug general/29093] New: clang fails to compile 0.187: error.c:50:17: yuri at tsoft dot com
2022-04-26 17:34 ` [Bug general/29093] clang fails to compile 0.187: error: format string is not a string literal yuri at tsoft dot com
2022-04-26 18:04 ` mark at klomp dot org [this message]

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-29093-10460-TAq98sHR7T@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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).