public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vvinayag at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/26677] New: valid-expr.h:65:20: error: type/value mismatch
Date: Tue, 29 Sep 2020 10:18:05 +0000	[thread overview]
Message-ID: <bug-26677-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26677
           Summary: valid-expr.h:65:20: error: type/value mismatch
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: vvinayag at arm dot com
  Target Milestone: ---

Relevant to patch [1], I am seeing error: type/value mismatch from
valid-expr.h:65:20 when building GDB with:
Build: aarch64-none-linux-gnu
Host: aarch64-none-linux-gnu
Target: aarch64-none-linux-gnu


In file included from
binutils-gdb--gdb/gdb/unittests/offset-type-selftests.c:24:0:
/binutils-gdb--gdb/gdb/unittests/offset-type-selftests.c: In substitution of
'template<class Expected, template<class ...> class Op, class ... Args> using
is_detected_exact = std::is_same<Expected, typename
gdb::detection_detail::detector<gdb::nonesuch, void, Op, Args ...>::type> [with
Expected = selftests::offset_type::off_A&; Op =
selftests::offset_type::check_valid_expr75::archetype; Args =
{selftests::offset_type::off_A, selftests::offset_type::off_B}]':

/binutils-gdb--gdb/gdb/unittests/offset-type-selftests.c:75:1:   required from
here
/binutils-gdb--gdb/gdb/../gdbsupport/valid-expr.h:65:20: error: type/value
mismatch at argument 2 in template parameter list for 'template<class Expected,
template<class ...> class Op, class ... Args> using is_detected_exact =
std::is_same<Expected, typename gdb::detection_detail::detector<gdb::nonesuch,
void, Op, Args ...>::type>'
    archetype, TYPES>::value == VALID,   \
                    ^
/binutils-gdb--gdb/gdb/../gdbsupport/valid-expr.h:79:3: note: in expansion of
macro 'CHECK_VALID_EXPR_INT'
   CHECK_VALID_EXPR_INT (ESC_PARENS(typename T1, typename T2),  \
   ^~~~~~~~~~~~~~~~~~~~
/binutils-gdb--gdb/gdb/unittests/offset-type-selftests.c:42:3: note: in
expansion of macro 'CHECK_VALID_EXPR_2'
   CHECK_VALID_EXPR_2 (off_A, off_B, VALID, EXPR_TYPE, EXPR)
   ^~~~~~~~~~~~~~~~~~


I observe this error when building on an aarch64-none-linux-gnu machine,
running ubuntu 14.04.5.
The compiler it is using is aarch64-none-linux-gnu-gcc version 6.4.1.


[1]
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1945192cb9a6184fb805d514ce4ca1bc8999b587


Regards,
Vasee

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

             reply	other threads:[~2020-09-29 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 10:18 vvinayag at arm dot com [this message]
2020-09-29 10:19 ` [Bug c++/26677] " vvinayag at arm dot com
2020-09-29 10:21 ` vvinayag at arm dot com
2022-02-19 16:47 ` tromey at sourceware dot org
2022-04-02 16:32 ` [Bug build/26677] " tromey at sourceware dot org
2022-04-15 13:40 ` tromey at sourceware dot org
2023-08-28 13:58 ` tromey at sourceware dot 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-26677-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).