[llvm-bugs] [Bug 46033] New: clang segfault with tuple get and overloaded ==

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=46033

            Bug ID: 46033
           Summary: clang segfault with tuple get and overloaded ==
           Product: clang
           Version: 9.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: mexx at sunrise.ch
                CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org,
                    neeilans at live.com, richard-llvm at metafoo.co.uk

Created attachment 23518
  --> https://bugs.llvm.org/attachment.cgi?id=23518&action=edit
source code (original an preprocessed), and clang output

compiling the attached crashtest.cc file crashes clang with a segmentation
fault. The offending part seems to be the comparison between the two results of
"get<0>" in main:

   std::cout << (std::get<0>(t1) == std::get<0>(t2)) << std::endl;

changing this line to the following compiles without error:

   std::cout << (std::get<0>(t1).get() == std::get<0>(t2).get()) << std::endl;

so I'm guessing it has to do with the lookup of the overloaded operator== for
the maybe<> template.

Reproduced with clang 6.0 and clang 9.0 (debian packages on Linux Mint xfvm)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200522/877ca4f3/attachment.html>