[llvm-bugs] [Bug 44615] New: -fconcepts-ts causes incorrect name lookup for non-type template parameter

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44615

Bug ID: 44615
   Summary: -fconcepts-ts causes incorrect name lookup for
non-type template parameter
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++2a
  Assignee: unassignedclangb...@nondot.org
  Reporter: da...@doublewise.net
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk

The following code

```
namespace s {
using t = int;
};

template
void f();
```

when compiled with

`clang++ -Xclang -fconcepts-ts -std=c++2a -c main.cpp`

at revision bb9b964


does not actually look up `t` in `s`. Instead, it looks it up in the global
scope, and thus it gives an error of

```
main.cpp:6:13: error: unknown type name 't'; did you mean 's::t'?
template
^
s::t
main.cpp:2:8: note: 's::t' declared here
using t = int;
  ^
1 error generated.
```

If I define a `t` in the global scope as well, it picks up that name and
compiles, using that variable instead. This is demonstrated by the following
program:


```
#include 

namespace s {
using t = int;
};

using t = short;

template
void f() {
static_assert(std::is_same_v);
}

void g() {
f<0>();
}
```


This behavior occurs only if `-Xclang -fconcepts-ts` is passed, but it seems
that this flag is necessary to actually get all of the concepts implementation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44616] New: Compiler crash on dependent type missing typename

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44616

Bug ID: 44616
   Summary: Compiler crash on dependent type missing typename
   Product: clang
   Version: trunk
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: sidney.cong...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

Possible duplicate of bug '16926'.

Clang crashes when instanciating a dependent type without writing 'typename'.
Crashes on Clang 3.0.0 as well as Clang trunk.

The invalid code:

template 
struct bla {
template 
using blo = U;
};

template 
constexpr bool pred() {
return /*typename*/ bla::template blo{};
}

int main() {
return pred();
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 39769] Generic lambda in variable template in class template does not compile

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39769

Sidney Congard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44613] Assertion failure with requires clause that mentions function parameter in class template

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44613

Saar Raz  changed:

   What|Removed |Added

 CC||saar@raz.email
   Assignee|unassignedclangbugs@nondot. |saar@raz.email
   |org |
 Fixed By Commit(s)||45538b5fb280e5b2903f7924fd4
   ||fa5b07a6dd3ea
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44613] Assertion failure with requires clause that mentions function parameter in class template

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44613

Saar Raz  changed:

   What|Removed |Added

 CC||saar@raz.email
   Assignee|unassignedclangbugs@nondot. |saar@raz.email
   |org |
 Fixed By Commit(s)||45538b5fb280e5b2903f7924fd4
   ||fa5b07a6dd3ea
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44619] New: SEGV on erroneous input

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44619

Bug ID: 44619
   Summary: SEGV on erroneous input
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: jan.kratoch...@redhat.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

It prints an error but then it crashes.
I cannot provide a preprocessed source as -E does not produce anything.
If I remove compilation error the crash no longer happens.
Tested on updated Fedora 30 x86_64.

clang++ -c -o /dev/null -D'throw(...)=noexcept(false)'
/usr/include/glibmm-2.4/glibmm/variant.h -I/usr/include/glibmm-2.4 -isystem
/usr/include -std=c++17

clang-10: warning: treating 'c-header' input as 'c++-header' when in C++ mode,
this behavior is deprecated [-Wdeprecated]
/usr/include/glibmm-2.4/glibmm/variant.h:23:10: fatal error: 'glibmmconfig.h'
file not found
#include 
 ^~~~
clang++:
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/SourceManager.cpp:840:
clang::FileID clang::SourceManager::getFileIDLoaded(unsigned int) const:
Assertion `0 && "Invalid SLocOffset or bad function choice"' failed.
Stack dump:
0.  Program arguments:
/home/jkratoch/redhat/llvm-monorepo-gccassertdebug/bin/clang++ -c -o /dev/null
-Dthrow(...)=noexcept(false) /usr/include/glibmm-2.4/glibmm/variant.h
-I/usr/include/glibmm-2.4 -isystem /usr/include -std=c++17 
1. 
/usr/lib/gcc/x86_64-redhat-linux/9/../../../../include/c++/9/bits/stl_map.h:1427:8:
at annotation token
2. 
/usr/lib/gcc/x86_64-redhat-linux/9/../../../../include/c++/9/ostream:41:1:
parsing namespace 'std'
3. 
/usr/lib/gcc/x86_64-redhat-linux/9/../../../../include/c++/9/bits/stl_map.h:66:1:
parsing namespace 'std::std'
 #0 0x04952f6e llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/home/jkratoch/redhat/llvm-monorepo/llvm/lib/Support/Unix/Signals.inc:564:22
 #1 0x04953001 PrintStackTraceSignalHandler(void*)
/home/jkratoch/redhat/llvm-monorepo/llvm/lib/Support/Unix/Signals.inc:625:1
 #2 0x049510a6 llvm::sys::RunSignalHandlers()
/home/jkratoch/redhat/llvm-monorepo/llvm/lib/Support/Signals.cpp:68:20
 #3 0x049528a7 llvm::sys::CleanupOnSignal(unsigned long)
/home/jkratoch/redhat/llvm-monorepo/llvm/lib/Support/Unix/Signals.inc:361:31
 #4 0x0486e332 (anonymous
namespace)::CrashRecoveryContextImpl::HandleCrash(int, unsigned long)
/home/jkratoch/redhat/llvm-monorepo/llvm/lib/Support/CrashRecoveryContext.cpp:80:5
 #5 0x0486e77b CrashRecoverySignalHandler(int)
/home/jkratoch/redhat/llvm-monorepo/llvm/lib/Support/CrashRecoveryContext.cpp:362:1
 #6 0x7fa5300dac70 __restore_rt (/lib64/libpthread.so.0+0x12c70)
 #7 0x7fa52e217e35 raise
/usr/src/debug/glibc-2.29-51-g845278f2c6/signal/../sysdeps/unix/sysv/linux/raise.c:51:1
 #8 0x7fa52e202895 abort
/usr/src/debug/glibc-2.29-51-g845278f2c6/stdlib/abort.c:81:7
 #9 0x7fa52e202769 _nl_load_domain.cold
/usr/src/debug/glibc-2.29-51-g845278f2c6/intl/loadmsgcat.c:1177:9
#10 0x7fa52e210566 (/lib64/libc.so.6+0x30566)
#11 0x04b75aa9 clang::SourceManager::getFileIDLoaded(unsigned int)
const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/SourceManager.cpp:849:7
#12 0x04b757aa clang::SourceManager::getFileIDSlow(unsigned int) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/SourceManager.cpp:740:1
#13 0x04b63f6c clang::SourceManager::getFileID(clang::SourceLocation)
const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/include/clang/Basic/SourceManager.h:1098:3
#14 0x04b64019
clang::SourceManager::getDecomposedLoc(clang::SourceLocation) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/include/clang/Basic/SourceManager.h:1239:31
#15 0x04b5f1f0
clang::DiagnosticsEngine::DiagStateMap::lookup(clang::SourceManager&,
clang::SourceLocation) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/Diagnostic.cpp:202:67
#16 0x04b6e490
clang::DiagnosticsEngine::GetDiagStateForLoc(clang::SourceLocation) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/include/clang/Basic/Diagnostic.h:414:56
#17 0x04b6d379 clang::DiagnosticIDs::getDiagnosticSeverity(unsigned
int, clang::SourceLocation, clang::DiagnosticsEngine const&) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/DiagnosticIDs.cpp:428:64
#18 0x04b6d311 clang::DiagnosticIDs::getDiagnosticLevel(unsigned int,
clang::SourceLocation, clang::DiagnosticsEngine const&) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/DiagnosticIDs.cpp:409:17
#19 0x04b6dd56
clang::DiagnosticIDs::ProcessDiag(clang::DiagnosticsEngine&) const
/quad/home/jkratoch/redhat/llvm-monorepo/clang/lib/Basic/DiagnosticIDs.cpp:637:25
#20 0x04b636

[llvm-bugs] [Bug 44621] New: LLDB may use wrong operand size of DW_OP_call_ref

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44621

Bug ID: 44621
   Summary: LLDB may use wrong operand size of DW_OP_call_ref
   Product: lldb
   Version: 10.0
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-...@lists.llvm.org
  Reporter: ikud...@accesssoftek.com
CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org

In lldb/source/Expression/DWARFExpression.cpp, GetOpcodeDataSize(),
DW_OP_call_ref is handled in the same way as DW_OP_addr:

  switch (op) {
  case DW_OP_addr:
  case DW_OP_call_ref: // 0x9a 1 address sized offset of DIE (DWARF3)
return data.GetAddressByteSize();

According to the DWARF standard, the operand size of DW_OP_call_ref is 4 or 8
bytes depending on the DWARF format (32- or 64-bit) and not an address size on
the target machine, as for DW_OP_addr.

Admittedly, I do not have a sample. I found that reviewing the code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44622] New: fneg (xor X -2147483648) -> X fold is missing in IR

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44622

Bug ID: 44622
   Summary: fneg (xor X -2147483648) -> X fold is missing in IR
   Product: new-bugs
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Keywords: code-quality
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: nok.ra...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org

define float @foo(float %0) {
  %2 = fneg float %0
  %3 = bitcast float %2 to i32
  %4 = xor i32 %3, -2147483648
  %5 = bitcast i32 %4 to float
  %6 = fneg float %5
  %7 = bitcast float %6 to i32
  %8 = xor i32 %7, -2147483648
  %9 = bitcast i32 %8 to float
  ret float %9
}

Adding fast flag to fneg does not help.

https://godbolt.org/z/o9WQYp

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44623] New: Backport RISC-V LTO Patches

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44623

Bug ID: 44623
   Summary: Backport RISC-V LTO Patches
   Product: new-bugs
   Version: 10.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: selli...@lowrisc.org
CC: a...@lowrisc.org, htmldevelo...@gmail.com,
llvm-bugs@lists.llvm.org
Blocks: 44555

Please may the following patches to the RISC-V backend be backported to LLVM
10.0:

- https://reviews.llvm.org/D72755
- https://reviews.llvm.org/D72768
- https://reviews.llvm.org/D70837 (not landed on master, but a fix to an
existing bug that is on the 10.0 branch)


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=44555
[Bug 44555] [meta] 10.0.0 Release Blockers
-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44624] New: Cast from _Complex int to _Complex double causes crash

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44624

Bug ID: 44624
   Summary: Cast from _Complex int to _Complex double causes crash
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: LLVM Codegen
  Assignee: unassignedclangb...@nondot.org
  Reporter: bevin.hans...@ericsson.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk

The code:

  _Complex int a;
  void fn1() { (_Complex double) a; }

causes a crash in Clang. This can be reproduced all the way to Clang 3.0.

Godbolt: https://godbolt.org/z/rajvzs

Stack dump:
0.  Program arguments: /opt/compiler-explorer/clang-trunk/bin/clang -g -o
./output.s -mllvm --x86-asm-syntax=intel -S
--gcc-toolchain=/opt/compiler-explorer/gcc-9.2.0 -fcolor-diagnostics
-fno-crash-diagnostics  
1.   parser at end of file
2.  :2:6: LLVM IR generation of declaration 'fn1'
3.  :2:6: Generating code for declaration 'fn1'
 #0 0x5638efe2ef1a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2883f1a)
 #1 0x5638efe2caf4 llvm::sys::RunSignalHandlers()
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2881af4)
 #2 0x5638efe2cd65 llvm::sys::CleanupOnSignal(unsigned long)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2881d65)
 #3 0x5638efda9cc4 (anonymous
namespace)::CrashRecoveryContextImpl::HandleCrash(int, unsigned long)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x27fecc4)
 #4 0x5638efdaa1e4 CrashRecoverySignalHandler(int)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x27ff1e4)
 #5 0x7f47d942b890 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
 #6 0x5638f0325818 (anonymous
namespace)::ScalarExprEmitter::EmitScalarConversion(llvm::Value*,
clang::QualType, clang::QualType, clang::SourceLocation, (anonymous
namespace)::ScalarExprEmitter::ScalarConversionOpts)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2d7a818)
 #7 0x5638f0327a36
clang::CodeGen::CodeGenFunction::EmitScalarConversion(llvm::Value*,
clang::QualType, clang::QualType, clang::SourceLocation)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2d7ca36)
 #8 0x5638f031b9da (anonymous
namespace)::ComplexExprEmitter::EmitCast(clang::CastKind, clang::Expr*,
clang::QualType) (/opt/compiler-explorer/clang-trunk/bin/clang+0x2d709da)
 #9 0x5638f0319f4c (anonymous
namespace)::ComplexExprEmitter::Visit(clang::Expr*)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2d6ef4c)
#10 0x5638f031b544
clang::CodeGen::CodeGenFunction::EmitComplexExpr(clang::Expr const*, bool,
bool) (/opt/compiler-explorer/clang-trunk/bin/clang+0x2d70544)
#11 0x5638f02df831 clang::CodeGen::CodeGenFunction::EmitAnyExpr(clang::Expr
const*, clang::CodeGen::AggValueSlot, bool)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2d34831)
#12 0x5638f02f147e
clang::CodeGen::CodeGenFunction::EmitIgnoredExpr(clang::Expr const*)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2d4647e)
#13 0x5638f00a7de3 clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt
const*, llvm::ArrayRef)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2afcde3)
#14 0x5638f00a841c
clang::CodeGen::CodeGenFunction::EmitCompoundStmtWithoutScope(clang::CompoundStmt
const&, bool, clang::CodeGen::AggValueSlot)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2afd41c)
#15 0x5638f00e8101
clang::CodeGen::CodeGenFunction::EmitFunctionBody(clang::Stmt const*)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2b3d101)
#16 0x5638f00f141e
clang::CodeGen::CodeGenFunction::GenerateCode(clang::GlobalDecl,
llvm::Function*, clang::CodeGen::CGFunctionInfo const&)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2b4641e)
#17 0x5638f0131261
clang::CodeGen::CodeGenModule::EmitGlobalFunctionDefinition(clang::GlobalDecl,
llvm::GlobalValue*) (/opt/compiler-explorer/clang-trunk/bin/clang+0x2b86261)
#18 0x5638f012ecd5
clang::CodeGen::CodeGenModule::EmitGlobalDefinition(clang::GlobalDecl,
llvm::GlobalValue*) (/opt/compiler-explorer/clang-trunk/bin/clang+0x2b83cd5)
#19 0x5638f012f3a3
clang::CodeGen::CodeGenModule::EmitGlobal(clang::GlobalDecl)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2b843a3)
#20 0x5638f01349f7
clang::CodeGen::CodeGenModule::EmitTopLevelDecl(clang::Decl*) (.part.4744)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x2b899f7)
#21 0x5638f0b36491 (anonymous
namespace)::CodeGeneratorImpl::HandleTopLevelDecl(clang::DeclGroupRef)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x358b491)
#22 0x5638f0b29ae6
clang::BackendConsumer::HandleTopLevelDecl(clang::DeclGroupRef)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x357eae6)
#23 0x5638f1547e34 clang::ParseAST(clang::Sema&, bool, bool)
(/opt/compiler-explorer/clang-trunk/bin/clang+0x3f9ce34)
#24 0x5638f0597f29 clang::FrontendAction::Execute()
(/opt/compiler-explorer/

[llvm-bugs] [Bug 7759] Crash in CallGraphSCCPass with -argpromotion -loop-extract-single

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=7759

Ehud Katz  changed:

   What|Removed |Added

 Resolution|WONTFIX |DUPLICATE
 CC||ehudk...@gmail.com

--- Comment #3 from Ehud Katz  ---


*** This bug has been marked as a duplicate of bug 8929 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 31106] opt crashes while running "CallGraph Pass Manager": Assertion `CallSites.empty() && "Dangling pointers found in call sites map"' failed

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=31106

Ehud Katz  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #9 from Ehud Katz  ---


*** This bug has been marked as a duplicate of bug 8929 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44625] New: segfault with -ftime-trace when output file cannot be opened

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44625

Bug ID: 44625
   Summary: segfault with -ftime-trace when output file cannot be
opened
   Product: clang
   Version: 9.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: jonathan.poe...@gmail.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk

clang -ftime-trace -c anything.cpp -o folder_that_does_not_exist/a.o

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44337] IR with double constant doesn't work with OrcJIT build by MSVC

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44337

Lang Hames  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #24 from Lang Hames  ---
> I have ported your patch from #40074 to LLVM 9.0.0 and tested it in the mine 
> environment.
> Your patch is working fine for me.
> Also, it fixes bug #44336.

That's great news. :)
Ok -- closing this as fixed by 84217ad6611.

> But are you sure that it is a good idea to pass a parameter by value?
> Error defineMaterializing(SymbolFlagsMap SymbolFlags);
> If you don't want to modify the map, a constant reference is a better 
> solution, if you want to modify, a non-constant reference or pointer is more 
> applicable here, in my opinion.

The JITDylib::defineMaterializing method makes modifications to the map based
on what definitions are accepted and rejected, and returns these to
MaterializationResponsibilty::defineMaterializing so that it can update the
responsibility set. Since these modifications are not interesting to the
client, it makes sense to pass by value: It is cheap, and if the client does
not need their value any more then no copies are required.

> One more question for you: is removing a module from OrcJIT will be available 
> in LLVM 10?

Unfortunately support for removing modules will not make it in to LLVM 10. The
best solution for now is to maintain a separate ExecutionSession for code that
you want to throw away. I am working on removable module support, and hope to
get it in to LLVM 11.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44336] Basic OrcJIT functional doesn't work with MSVC

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44336

Lang Hames  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||lha...@gmail.com
 Status|NEW |RESOLVED

--- Comment #4 from Lang Hames  ---
Closing as fixed by 84217ad6611, based on discussion in
http://llvm.org/PR44337.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44337] IR with double constant doesn't work with OrcJIT build by MSVC

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44337
Bug 44337 depends on bug 44336, which changed state.

Bug 44336 Summary: Basic OrcJIT functional doesn't work with MSVC
https://bugs.llvm.org/show_bug.cgi?id=44336

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 40074] Duplicate definition of symbol error to do with mergable comdat constant symbols on Windows/COFF

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40074

Lang Hames  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #11 from Lang Hames  ---
Great! Thank you for checking this out Machiel.

Closing as fixed by 84217ad6611.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44626] New: [llvm-objdump] fails to disassemble as thumb

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44626

Bug ID: 44626
   Summary: [llvm-objdump] fails to disassemble as thumb
   Product: tools
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: llvm-objdump
  Assignee: unassignedb...@nondot.org
  Reporter: ndesaulni...@google.com
CC: kristof.be...@arm.com, llvm-bugs@lists.llvm.org,
peter.sm...@linaro.org, srhi...@google.com

I was getting super confused comparing the output of llvm-objdump to gdb's `x/i
` output for a 32b ARM Linux kernel until I realized that llvm-objdump
was printing disassembly as ARM, not thumb.  GNU objdump doesn't seem to have
this issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44627] New: Reversed candidate operator is not found by argument dependent lookup

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44627

Bug ID: 44627
   Summary: Reversed candidate operator is not found by argument
dependent lookup
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++2a
  Assignee: unassignedclangb...@nondot.org
  Reporter: da...@doublewise.net
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk

The following code

```
namespace n {

struct type {};

bool operator==(type lhs, int rhs) {
return true;
}

} // namespace n

void f() {
n::type() == 0;
0 == n::type(); // fails
}
```

fails to compile with the error message

```
:13:7: error: invalid operands to binary expression ('int' and
'n::type')

0 == n::type(); // fails

~ ^  ~

:5:6: note: candidate function not viable: no known conversion from
'int' to 'n::type' for 1st argument

bool operator==(type lhs, int rhs) {

 ^

1 error generated.

Compiler returned: 1
```

when compiled against clang trunk with `clang++ -std=c++2a -stdlib=libc++ -w`.
The same thing occurs for `<=>` and the other comparison operators. Note that
it succeeds if the definition of `f` is moved into `n`.

See it live: https://godbolt.org/z/pHwvw6

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44552, which changed state.

Bug 44552 Summary: opt -instcombine hits "LLVM ERROR: Instruction Combining 
seems stuck in an infinite loop after 1000 iterations."
https://bugs.llvm.org/show_bug.cgi?id=44552

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44552] opt -instcombine hits "LLVM ERROR: Instruction Combining seems stuck in an infinite loop after 1000 iterations."

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44552

Hans Wennborg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 CC||h...@chromium.org

--- Comment #5 from Hans Wennborg  ---
Cherry-picked to 10.x in 7adf83beece381d153f8b4a67fa341d13f9c4ba2

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 32203, which changed state.

Bug 32203 Summary: readability-braces-around-statements broken for if constexpr
https://bugs.llvm.org/show_bug.cgi?id=32203

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44229, which changed state.

Bug 44229 Summary: bugprone-branch-clone false positive with template functions 
and constexpr
https://bugs.llvm.org/show_bug.cgi?id=44229

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44559, which changed state.

Bug 44559 Summary: [SLP] Alternation with div/rem introduces potential UB
https://bugs.llvm.org/show_bug.cgi?id=44559

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44559] [SLP] Alternation with div/rem introduces potential UB

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44559

Hans Wennborg  changed:

   What|Removed |Added

 CC||h...@chromium.org
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #1 from Hans Wennborg  ---
Cherry-picked those two in d64ca7abe191e5813ab171df325f2cc2693dae21 and
029140ee1ca99e23558c774bb23257a4ea796069, respectively.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44576, which changed state.

Bug 44576 Summary: Merge caee96031d3be9f951e4a17c8d3fb1c8b748fb31 to 10.0 branch
https://bugs.llvm.org/show_bug.cgi?id=44576

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44576] Merge caee96031d3be9f951e4a17c8d3fb1c8b748fb31 to 10.0 branch

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44576

Hans Wennborg  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
 CC||h...@chromium.org

--- Comment #1 from Hans Wennborg  ---
This was cherry-picked in ac2c2db1674f200f87b05bee528c761600d87615

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44595, which changed state.

Bug 44595 Summary: Compilation fails on VS2019
https://bugs.llvm.org/show_bug.cgi?id=44595

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44612] libclang-cpp.so requires linking with --as-needed when clang is built with -DBUILD_SHARED_LIBS=ON

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44612

Hans Wennborg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||h...@chromium.org
 Status|NEW |RESOLVED

--- Comment #1 from Hans Wennborg  ---
Cherry-picked to 10.x in 3e429b691ec89de09324d6af33e35f1491f45b7d

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44612, which changed state.

Bug 44612 Summary: libclang-cpp.so requires linking with --as-needed when clang 
is built with -DBUILD_SHARED_LIBS=ON
https://bugs.llvm.org/show_bug.cgi?id=44612

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44555] [meta] 10.0.0 Release Blockers

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44612, which changed state.

Bug 44612 Summary: libclang-cpp.so requires linking with --as-needed when clang 
is built with -DBUILD_SHARED_LIBS=ON
https://bugs.llvm.org/show_bug.cgi?id=44612

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44612] libclang-cpp.so requires linking with --as-needed when clang is built with -DBUILD_SHARED_LIBS=ON

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44612

Tom Stellard  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #2 from Tom Stellard  ---
I just had to revert this commit in trunk.  It uses a cmake 3.6 feature, and
llvm only requires 3.4.3 or newer.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 44488] Miscompile with opt -loop-vectorize

2020-01-22 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44488

Florian Hahn  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Fixed By Commit(s)||f14f2a856802e086662d919e2ea
   ||d641718b27555
 Status|NEW |RESOLVED

--- Comment #7 from Florian Hahn  ---
Should be fixed by https://reviews.llvm.org/rGf14f2a856802

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs