public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "gmoreira at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/23829] Bug introduced in bpf -base.cxx in git master
Date: Fri, 26 Oct 2018 05:47:00 -0000	[thread overview]
Message-ID: <bug-23829-6586-7j5pn2Iwx5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23829-6586@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Gustavo Moreira <gmoreira at gmail dot com> ---
Other errors related to the same merge:

bpf-translate.cxx: In member function ‘size_t
bpf::bpf_unparser::parse_asm_stmt(embeddedcode*, size_t, bpf::asm_stmt&)’:
util.h:62:59: error: format ‘%lu’ expects argument of type ‘long unsigned int’,
but argument 2 has type ‘std::vector<std::__cxx11::basic_string<char>
>::size_type {aka unsigned int}’ [-Werror=format=]
 #define _F(format, ...) autosprintf(_(format), __VA_ARGS__)
                                                           ^
util.h:68:53: note: in definition of macro ‘SEMANTIC_ERROR’
 #define SEMANTIC_ERROR(...) semantic_error(ERR_SRC, __VA_ARGS__)
                                                     ^~~~~~~~~~~
bpf-translate.cxx:839:31: note: in expansion of macro ‘_F’
         throw SEMANTIC_ERROR (_F("invalid bpf embeddedcode syntax (label
expects 1 arg, found %lu)", args.size()-1), stmt.tok);
                               ^~
util.h:62:59: error: format ‘%lu’ expects argument of type ‘long unsigned int’,
but argument 2 has type ‘std::vector<std::__cxx11::basic_string<char>
>::size_type {aka unsigned int}’ [-Werror=format=]
 #define _F(format, ...) autosprintf(_(format), __VA_ARGS__)
                                                           ^
util.h:68:53: note: in definition of macro ‘SEMANTIC_ERROR’
 #define SEMANTIC_ERROR(...) semantic_error(ERR_SRC, __VA_ARGS__)
                                                     ^~~~~~~~~~~
bpf-translate.cxx:846:31: note: in expansion of macro ‘_F’
         throw SEMANTIC_ERROR (_F("invalid bpf embeddedcode syntax (alloc
expects 2 args, found %lu)", args.size()-1), stmt.tok);
                               ^~
util.h:62:59: error: format ‘%lu’ expects argument of type ‘long unsigned int’,
but argument 2 has type ‘std::vector<std::__cxx11::basic_string<char>
>::size_type {aka unsigned int}’ [-Werror=format=]
 #define _F(format, ...) autosprintf(_(format), __VA_ARGS__)
                                                           ^
util.h:68:53: note: in definition of macro ‘SEMANTIC_ERROR’
 #define SEMANTIC_ERROR(...) semantic_error(ERR_SRC, __VA_ARGS__)
                                                     ^~~~~~~~~~~
bpf-translate.cxx:854:31: note: in expansion of macro ‘_F’
         throw SEMANTIC_ERROR (_F("invalid bpf embeddedcode syntax (call
expects at least 2 args, found %lu)", args.size()-1), stmt.tok);
                               ^~
util.h:62:59: error: format ‘%lu’ expects argument of type ‘long unsigned int’,
but argument 2 has type ‘std::vector<std::__cxx11::basic_string<char>
>::size_type {aka unsigned int}’ [-Werror=format=]
 #define _F(format, ...) autosprintf(_(format), __VA_ARGS__)
                                                           ^
util.h:68:53: note: in definition of macro ‘SEMANTIC_ERROR’
 #define SEMANTIC_ERROR(...) semantic_error(ERR_SRC, __VA_ARGS__)
                                                     ^~~~~~~~~~~
bpf-translate.cxx:864:31: note: in expansion of macro ‘_F’
         throw SEMANTIC_ERROR (_F("invalid bpf embeddedcode syntax (opcode
expects 4 args, found %lu)", args.size()-1), stmt.tok);
                               ^~
bpf-translate.cxx: In member function ‘void
bpf::bpf_unparser::emit_asm_opcode(const bpf::asm_stmt&,
std::map<std::__cxx11::basic_string<char>, bpf::block*>)’:
bpf-translate.cxx:1084:14: error: ‘BPF_JLT’ was not declared in this scope
         case BPF_JLT: c = LTU; break;
              ^~~~~~~
bpf-translate.cxx:1085:14: error: ‘BPF_JLE’ was not declared in this scope
         case BPF_JLE: c = LEU; break;
              ^~~~~~~
bpf-translate.cxx:1088:14: error: ‘BPF_JSLT’ was not declared in this scope
         case BPF_JSLT: c = LT; break;
              ^~~~~~~~
bpf-translate.cxx:1089:14: error: ‘BPF_JSLE’ was not declared in this scope
         case BPF_JSLE: c = LE; break;
              ^~~~~~~~
In file included from staptree.h:27:0,
                 from bpf-internal.h:18,
                 from bpf-translate.cxx:10:
util.h:62:59: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘int64_t {aka long long int}’ [-Werror=format=]
 #define _F(format, ...) autosprintf(_(format), __VA_ARGS__)
                                                           ^
util.h:68:53: note: in definition of macro ‘SEMANTIC_ERROR’
 #define SEMANTIC_ERROR(...) semantic_error(ERR_SRC, __VA_ARGS__)
                                                     ^~~~~~~~~~~
bpf-translate.cxx:1127:27: note: in expansion of macro ‘_F’
     throw SEMANTIC_ERROR (_F("offset field '%ld' out of range in bpf code",
stmt.off), stmt.tok);
                           ^~
cc1plus: all warnings being treated as errors

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2018-10-26  5:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26  5:38 [Bug bpf/23829] New: " gmoreira at gmail dot com
2018-10-26  5:47 ` gmoreira at gmail dot com [this message]
2018-10-29 17:54 ` [Bug bpf/23829] " me at serhei dot io
2018-10-29 17:54 ` me at serhei dot io
2018-10-31  1:02 ` gmoreira at gmail dot com
2018-10-31  1:03 ` gmoreira at gmail dot com
2018-11-02 20:51 ` me at serhei dot io
2019-03-22 19:09 ` me at serhei dot io
2019-03-27 14:48 ` me at serhei dot io

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-23829-6586-7j5pn2Iwx5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).