public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/100207] Error in build()
Date: Thu, 22 Apr 2021 13:42:07 +0000	[thread overview]
Message-ID: <bug-100207-4-YBJIyBiUx1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100207-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #3)
> (In reply to sujay1844 from comment #2)
> > So is the AUR package having a bug??
> 
> What's AUR? Can you investigate what sets the -Wformat-security ?

Presumably it's this:
  https://wiki.archlinux.org/index.php/Arch_User_Repository
Sounds like AUR is injecting -Werror=format-security.

The strings in question come from:

          const char *message = CPP_OPTION (pfile, cplusplus) 
                                ? N_("use of C++11 long long integer constant")
                                : N_("use of C99 long long integer constant");

and:

          const char *message = (result & CPP_N_UNSIGNED) == CPP_N_UNSIGNED
                                ? N_("use of C++23 %<size_t%> integer
constant")
                                : N_("use of C++23 %<make_signed_t<size_t>%>
integer constant");

which appear to be safe to me.

  parent reply	other threads:[~2021-04-22 13:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 12:03 [Bug jit/100207] New: " sujay1844 at protonmail dot com
2021-04-22 12:30 ` [Bug jit/100207] " marxin at gcc dot gnu.org
2021-04-22 12:31 ` sujay1844 at protonmail dot com
2021-04-22 12:38 ` marxin at gcc dot gnu.org
2021-04-22 13:42 ` dmalcolm at gcc dot gnu.org [this message]
2021-04-22 13:46 ` [Bug jit/100207] -Werror=format-security error in AUR build of libgccjit dmalcolm at gcc dot gnu.org
2021-04-22 13:48 ` sujay1844 at protonmail dot com
2021-04-22 13:49 ` sujay1844 at protonmail dot com
2021-04-22 13:49 ` sujay1844 at protonmail dot com
2021-04-22 13:52 ` sujay1844 at protonmail dot com
2021-04-22 14:09 ` dmalcolm at gcc dot gnu.org
2021-04-22 14:12 ` sujay1844 at protonmail dot com
2021-04-22 14:19 ` dmalcolm at gcc dot gnu.org
2021-04-22 14:21 ` sujay1844 at protonmail dot com
2021-04-22 15:04 ` dmalcolm at gcc dot gnu.org
2021-04-22 15:27 ` sujay1844 at protonmail dot com
2021-05-10  0:43 ` jonathon at m2x dot dev
2021-05-10  1:18 ` sujay1844 at protonmail dot com
2021-05-10  1:34 ` jonathon at m2x dot dev
2021-05-10  1:36 ` sujay1844 at protonmail dot com
2021-05-10  1:39 ` sujay1844 at protonmail dot com

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-100207-4-YBJIyBiUx1@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).