[llvm-bugs] [Bug 38930] Segmentation fault

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=38930

we...@wsoptics.de changed:

   What|Removed |Added

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

--- Comment #1 from we...@wsoptics.de ---
This no longer segfaults at least in clang-11, so I'll close it.

-- 
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 50205] New: 12 regression: no return statement in constexpr function

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50205

Bug ID: 50205
   Summary: 12 regression: no return statement in constexpr
function
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++2a
  Assignee: unassignedclangb...@nondot.org
  Reporter: hewi...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk

constexpr double pow(double x, long long n) noexcept {
if (n > 0) [[likely]]
return x * pow(x, n - 1);
else [[unlikely]]
return 1;
}
constexpr long long fact(long long n) noexcept {
if (n > 1) [[likely]]
return n * fact(n - 1);
else [[unlikely]]
return 1;
}

:1:18: error: no return statement in constexpr function
constexpr double pow(double x, long long n) noexcept {
 ^
:7:21: error: no return statement in constexpr function
constexpr long long fact(long long n) noexcept {
^

https://godbolt.org/z/ezMsrhrxo

-- 
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] Issue 33892 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::addUsingDirectives

2021-05-03 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #1 on issue 33892 by ClusterFuzz-External: llvm:clang-fuzzer: 
Stack-overflow in UnqualUsingDirectiveSet::addUsingDirectives
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33892#c1

ClusterFuzz testcase 4812243674988544 is verified as fixed in 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202105020605:202105030618

If this is incorrect, please file a bug on 
https://github.com/google/oss-fuzz/issues/new

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 50019] AllowShortIfStatementsOnASingleLine don't work with else if constexpr statement

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50019

Marek Kurdej  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
 Fixed By Commit(s)||8d93d7ffedebc5f18dee22ba954
   ||d38a1d2d0affa

--- Comment #2 from Marek Kurdej  ---
Fixed in https://reviews.llvm.org/rG8d93d7ffedebc5f18dee22ba954d38a1d2d0affa.
You'd need to use `AllowShortIfStatementsOnASingleLine: AllIfsAndElse` because
`AllowShortIfStatementsOnASingleLine: Always` has kept the old behaviour not to
break the backwards compatibility.

-- 
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 50206] New: clang assert on the constexpr variable of omp clause is not marked as used

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50206

Bug ID: 50206
   Summary: clang assert on the constexpr variable of omp clause
is not marked as used
   Product: OpenMP
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Clang Compiler Support
  Assignee: unassignedclangb...@nondot.org
  Reporter: jennifer...@intel.com
CC: llvm-bugs@lists.llvm.org

Created attachment 24823
  --> https://bugs.llvm.org/attachment.cgi?id=24823&action=edit
Test to reproduce the problem.

Attached test assert in clang

cmplrllvm-27165>clang -cc1 -fopenmp -fopenmp-version=50
-fopenmp-targets=x86_64-pc-linux-gnu -x c++ -emit-llvm -o - j1.cpp
clang: /localdisk2/jyu2/git/llorg/llvm/clang/lib/CodeGen/CGExpr.cpp:2765:
clang::CodeGen::LValue clang::CodeGen::CodeGenFunction::EmitDeclRefLValue(const
clang::DeclRefExpr*): Assertion `(ND->isUsed(false) || !isa(ND) ||
E->isNonOdrUse() || !E->getLocation().isValid()) && "Should not use decl
without marking it used!"' failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0.  Program arguments: clang -cc1 -fopenmp -fopenmp-version=50
-fopenmp-targets=x86_64-pc-linux-gnu -x c++ -emit-llvm -o - j1.cpp
1.   parser at end of file
2.  Per-file LLVM IR generation
3.  j1.cpp:4:6: Generating code for declaration 'test'

-- 
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 50207] New: call to constexpr variadic class member function is not emitted (and triggers warning)

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50207

Bug ID: 50207
   Summary: call to constexpr variadic class member function is
not emitted (and triggers warning)
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++2a
  Assignee: unassignedclangb...@nondot.org
  Reporter: ldalessan...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk

In the following example, the call to `foo` is not emitted.

```
struct Foo {
constexpr static int bar() {
return foo(42);
}

constexpr static int foo(int, auto...) { 
return 0;
}
};

// warning: inline function 'Foo::foo<>' is not defined [-Wundefined-inline]
int i = Foo::bar(); 
```

1. If I reorder the definitions of  `bar` and `foo` this works fine.
2. If I add some unused function `car` after the definition of `foo` this works
fine.
3. If foo is not a variadic template it works fine.
3. The `static`ness if the function is irrelevant, just makes the example
smaller.

See a working version at https://godbolt.org/z/dKqze6fKn.

-- 
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] Issue 33930 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::operator==

2021-05-03 Thread ClusterFuzz-External via monorail via llvm-bugs
Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, 
d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, 
llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, 
mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible 
Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-05-03
Type: Bug

New issue 33930 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow 
in llvm::FoldingSetNodeID::operator==
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33930

Detailed Report: https://oss-fuzz.com/testcase?key=4647297309868032

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: clang-objc-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffe443408e8
Crash State:
  llvm::FoldingSetNodeID::operator==
  llvm::FoldingSetBase::FindNodeOrInsertPos
  clang::ASTContext::getFunctionNoProtoType
  
Sanitizer: address (ASAN)

Regressed: 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202103160614:202103170627

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4647297309868032

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for 
instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any 
stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other 
feedback, please file an issue at https://github.com/google/oss-fuzz/issues. 
Comments on individual Monorail issues are not monitored.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 50208] New: instCombine: incorrect fold of pointer comparison between globals

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50208

Bug ID: 50208
   Summary: instCombine: incorrect fold of pointer comparison
between globals
   Product: libraries
   Version: trunk
  Hardware: All
OS: All
Status: NEW
  Keywords: miscompilation
  Severity: normal
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: nunoplo...@sapo.pt
CC: juneyoung@sf.snu.ac.kr, llvm-bugs@lists.llvm.org,
nikita@gmail.com, spatel+l...@rotateright.com

test: Transforms/InstSimplify/ConstProp/icmp-null.ll
The transformation below is only correct if the gep is over i8*, and not with
non-byte-sized types. This is correct: https://alive2.llvm.org/ce/z/S_TsHW


@g2 = global 4 bytes, align 4
@g = global 8 bytes, align 4

define i1 @null_gep_ne_global() {
  %__constexpr_0 = ptrtoint * @g2 to i64
  %gep = gep * null, 8 x i64 %__constexpr_0  ; <-- notice the 8 x
  %cmp = icmp ne * %gep, @g
  ret i1 %cmp
}
=>
@g2 = global 4 bytes, align 4
@g = global 8 bytes, align 4

define i1 @null_gep_ne_global() {
  ret i1 1
}
Transformation doesn't verify!

ERROR: Value mismatch

Example:

Source:
i64 %__constexpr_0 = #x924925b6db6f5564 (10540997870133138788,
-7905746203576412828)
* %gep = pointer(non-local, block_id=0, offset=-7905737407482647776)
i1 %cmp = #x0 (0)

SOURCE MEMORY STATE
===
NON-LOCAL BLOCKS:
Block 0 >   size: 0 align: 1alloc type: 0   address: 0
Block 1 >   size: 4 align: 4alloc type: 0   address:
10540997870133138788
Block 2 >   size: 8 align: 4alloc type: 0   address:
1054100226903840

Target:
Source value: #x0 (0)
Target value: #x1 (1)

-- 
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 50209] New: Lambda function names generated by Clang does not conform to ABI

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50209

Bug ID: 50209
   Summary: Lambda function names generated by Clang does not
conform to ABI
   Product: clang
   Version: trunk
  Hardware: All
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: lxf...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

When compiling lambda functions, the generated function
names use different conventions than GCC.
Example: https://godbolt.org/z/5qvqKqEe6
The lambda in Clang is named "_Z3barIZ3foovE3$_0EvT_", while the one
in GCC is named "_Z3barIZ3foovEUlvE_EvT_". Their demangled names are
also different ("void bar(foo()::$_0)" vs "void
bar(foo()::{lambda()#1})").

Discussions in clang-dev:
https://lists.llvm.org/pipermail/cfe-dev/2021-May/068080.html

-- 
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 50211] New: ThinLTO + lld taking much longer linking Android libqcrilNr.so, comparing against full LTO + lld

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50211

Bug ID: 50211
   Summary: ThinLTO + lld taking much longer linking Android
libqcrilNr.so, comparing against full LTO + lld
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: AArch64
  Assignee: unassignedb...@nondot.org
  Reporter: huih...@quicinc.com
CC: arnaud.degrandmai...@arm.com,
llvm-bugs@lists.llvm.org, smithp...@googlemail.com,
ties.st...@arm.com

When linking 64bit Android library libqcrilNr.so, using in house llvm compiler,
code base similar to community release/12.X. Observing ThinLTO link time taking
much longer than full lto.

When link with full lto, takes around 5 minutes.
When link with thin lto, takes around 17 minutes.

I can't really figure out why thin lto is taking much longer. Seeking help
here, see if anyone more familiar with this issue, or knowing which part of
llvm could possibly contribute to this slow down?

Can't really share any object file here. But sharing the time reports, hope
this can help.

Time report for full lto:
===-===
  ... Pass execution timing report ...
===-===
  Total Execution Time: 444.9100 seconds (444.2988 wall clock)

   ---User Time---   --System Time--   --User+System--   ---Wall Time---  ---
Name ---
  69.7080 ( 22.6%)  28.3786 ( 20.8%)  98.0866 ( 22.0%)  98.0891 ( 22.1%) 
AArch64 Assembly Printer
  33.5838 ( 10.9%)  13.1880 (  9.7%)  46.7717 ( 10.5%)  46.6892 ( 10.5%) 
AArch64 Instruction Selection
  14.8625 (  4.8%)   7.5726 (  5.6%)  22.4351 (  5.0%)  22.4490 (  5.1%) 
Machine Module Information
  13.1707 (  4.3%)   6.7261 (  4.9%)  19.8967 (  4.5%)  19.9138 (  4.5%) 
Dominator Tree Construction #7
  12.8369 (  4.2%)   6.6886 (  4.9%)  19.5255 (  4.4%)  19.5272 (  4.4%) 
Function Alias Analysis Results #4
  12.8099 (  4.2%)   6.6547 (  4.9%)  19.4646 (  4.4%)  19.4668 (  4.4%)  Basic
Alias Analysis (stateless AA impl) #4
   6.9480 (  2.3%)   3.2763 (  2.4%)  10.2243 (  2.3%)  10.2027 (  2.3%) 
Greedy Register Allocator
   6.2687 (  2.0%)   3.1288 (  2.3%)   9.3975 (  2.1%)   9.3346 (  2.1%) 
Prologue/Epilogue Insertion & Frame Finalization
   5.1671 (  1.7%)   2.3538 (  1.7%)   7.5209 (  1.7%)   7.4856 (  1.7%)  Live
DEBUG_VALUE analysis
   4.7978 (  1.6%)   2.1008 (  1.5%)   6.8986 (  1.6%)   6.8701 (  1.5%)  Live
Variable Analysis
   5.3652 (  1.7%)   0.9511 (  0.7%)   6.3163 (  1.4%)   6.2932 (  1.4%) 
Module Verifier #2
   5.1952 (  1.7%)   0.5094 (  0.4%)   5.7046 (  1.3%)   5.6843 (  1.3%) 
Module Verifier
   3.6007 (  1.2%)   1.5525 (  1.1%)   5.1533 (  1.2%)   5.1344 (  1.2%)  Live
Interval Analysis
   3.4184 (  1.1%)   1.5104 (  1.1%)   4.9288 (  1.1%)   4.8973 (  1.1%) 
Simple Register Coalescing
   3.2224 (  1.0%)   1.6417 (  1.2%)   4.8641 (  1.1%)   4.8603 (  1.1%) 
Machine Natural Loop Construction #2
   2.8867 (  0.9%)   1.4917 (  1.1%)   4.3784 (  1.0%)   4.3753 (  1.0%) 
MachineDominator Tree Construction #5
   3.0209 (  1.0%)   1.0482 (  0.8%)   4.0691 (  0.9%)   4.0510 (  0.9%) 
Memory SSA
   2.8420 (  0.9%)   1.1124 (  0.8%)   3.9544 (  0.9%)   3.9477 (  0.9%)  Free
MachineFunction
   2.0593 (  0.7%)   1.0078 (  0.7%)   3.0671 (  0.7%)   3.0524 (  0.7%) 
Insert stack protectors
   1.8488 (  0.6%)   0.8942 (  0.7%)   2.7430 (  0.6%)   2.7401 (  0.6%)  Slot
index numbering #2
   1.5921 (  0.5%)   0.7925 (  0.6%)   2.3846 (  0.5%)   2.3749 (  0.5%) 
MachineDominator Tree Construction
   1.4949 (  0.5%)   0.7285 (  0.5%)   2.2234 (  0.5%)   2.2182 (  0.5%) 
Machine Block Frequency Analysis #3
   1.5021 (  0.5%)   0.7089 (  0.5%)   2.2110 (  0.5%)   2.2009 (  0.5%) 
Branch Probability Analysis #2
   1.3685 (  0.4%)   0.7354 (  0.5%)   2.1039 (  0.5%)   2.0826 (  0.5%) 
Scalar Evolution Analysis
   1.3959 (  0.5%)   0.6686 (  0.5%)   2.0645 (  0.5%)   2.0621 (  0.5%) 
MachineDominator Tree Construction #2


For thin lto, observing single cpu running for the first 13 minutes, the later
4 minutes are multi-threaded.

===-===
  ... Pass execution timing report ...
===-===
  Total Execution Time: 122903.7639 seconds (7749.4743 wall clock)

   ---User Time---   --System Time--   --User+System--   ---Wall Time---  ---
Name ---
  304.7405 (  3.8%)   2.1033 (  0.0%)  306.8439 (  0.2%)  306.8722 (  4.0%) 
Lower type metadata
  289.0256 (  3.6%)   0.8153 (  0.0%)  289.8409 (  0.2%)  289.8686 (  3.7%) 
Branch Probability Basic Block Placement
  190.9626 (  2.4%)   0.4888 (  0.0%)  191.4514 (  0.2%)  191.4685 (  2.

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49390, which changed state.

Bug 49390 Summary: BPF: backport 4 TTI cost function related commits
https://bugs.llvm.org/show_bug.cgi?id=49390

   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 49390] BPF: backport 4 TTI cost function related commits

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49390

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Fixed By Commit(s)|a260ae716  74975d35b|a260ae716  74975d35b
   |1959ead52 6d102f15a |1959ead52 6d102f15a
   ||3568d61f11e2 f9efff398c11
   ||2460947eefc2 6fe7c3728d1e
 Status|NEW |RESOLVED

--- Comment #2 from Tom Stellard  ---
Merged: 6fe7c3728d1e

-- 
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 49778] [InstCombine] Miscompile of (x & (~(-1 << x))) << x

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49778

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|5352490ce613f1bdedaf478765b |5352490ce613f1bdedaf478765b
   |089b1f0a8be0d   |089b1f0a8be0d
   |dceb3e599668496420d41b99310 |dceb3e599668496420d41b99310
   |0d23eeb7c0ada   |0d23eeb7c0ada
   |2760a808b9916a2839513b7fd73 |2760a808b9916a2839513b7fd73
   |14a464f52481e   |14a464f52481e 907a751a38ff
   ||4a4b1c75a1ea c27ad80507bf
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #13 from Tom Stellard  ---
Merged: c27ad80507bf

-- 
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 49317] [meta] 12.0.1 Release Blockers

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49778, which changed state.

Bug 49778 Summary: [InstCombine] Miscompile of (x & (~(-1 << x))) << x
https://bugs.llvm.org/show_bug.cgi?id=49778

   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 48902] [meta] 12.0.0 Release Blockers

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=48902
Bug 48902 depends on bug 49778, which changed state.

Bug 49778 Summary: [InstCombine] Miscompile of (x & (~(-1 << x))) << x
https://bugs.llvm.org/show_bug.cgi?id=49778

   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 49935] Cherry-pick 63bc9e443502ab6def2dec0b5ffe64a522f801cc to 12.x release

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49935

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|b9b708eef8cb7bcb073361283cd |b9b708eef8cb7bcb073361283cd
   |573beb04992a9   |573beb04992a9 0cbbf06b6256
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Tom Stellard  ---
Merged: 0cbbf06b6256

-- 
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 48902] [meta] 12.0.0 Release Blockers

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=48902
Bug 48902 depends on bug 49935, which changed state.

Bug 49935 Summary: Cherry-pick 63bc9e443502ab6def2dec0b5ffe64a522f801cc to 12.x 
release
https://bugs.llvm.org/show_bug.cgi?id=49935

   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 49317] [meta] 12.0.1 Release Blockers

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49935, which changed state.

Bug 49935 Summary: Cherry-pick 63bc9e443502ab6def2dec0b5ffe64a522f801cc to 12.x 
release
https://bugs.llvm.org/show_bug.cgi?id=49935

   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 50007] Backport 'Partially Revert "scan-view: Remove Reporter.py and associated AppleScript files"' to 12.0.1

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50007

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)|e3cd3a3c91524c957e06bb01703 |e3cd3a3c91524c957e06bb01703
   |43548f02b6842   |43548f02b6842 3263c81589ec

--- Comment #1 from Tom Stellard  ---
Merged: 3263c81589ec

-- 
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 49317] [meta] 12.0.1 Release Blockers

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 50007, which changed state.

Bug 50007 Summary: Backport 'Partially Revert "scan-view: Remove Reporter.py 
and associated AppleScript files"' to 12.0.1
https://bugs.llvm.org/show_bug.cgi?id=50007

   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 50212] New: llvm-project v12 does not work correctly with JIT-ed code for ARM64

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50212

Bug ID: 50212
   Summary: llvm-project v12 does not work correctly with JIT-ed
code for ARM64
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: release blocker
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: alex_fe...@ukr.net
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

Created attachment 24825
  --> https://bugs.llvm.org/attachment.cgi?id=24825&action=edit
It is simple example (JITtest) what demonstrates issue

I detected wrong work llvm-12 with JITed code for ARM64. (llvm-10 work
correctly)
I wrote a simple example (JITtest) that demonstrates issues and differences
between llvm-10 and llvm-12; between x86_64 and ARM64 for Ubuntu-20.

I created fn_lib.c file with one function, then created fn_lib.ll file (command
" clang -g -c -S -emit-llvm fn_lib.c ")
In jit_test.cpp I load fn_lib.ll (use llvm::parseIRFile), then created
llvm::ExecutionEngine, then founf my function (fn), create argumets and run my
function.
jit_test.cpp can be compile using command " clang++ -g jit_test.cpp -o jit_test
`llvm-config --cxxflags --ldflags --system-libs --libs all` "

This example work OK for clang-10/x86_64, clang-10/ARM64, clang-12/x86_64 BUT
does not work for clang-12/ARM64
At the bottom, I added console output for all cases. (for output logs I used
QEMU for ARM64 and VirtualBox for x86_64, but on real PC and real ARM64 output
the same)

Ubuntu 20, x86_64, clang-10


vub@vub:~/proj/JITtest$ lsb_release -a
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:focal
vub@vub:~/proj/JITtest$ clang++ -v
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/9
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/9
Candidate multilib: .;@m64
Selected multilib: .;@m64
vub@vub:~/proj/JITtest$ clang -v
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/9
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/9
Candidate multilib: .;@m64
Selected multilib: .;@m64
vub@vub:~/proj/JITtest$ ls
fn_lib.c  jit_test.cpp  ReadMe.txt
vub@vub:~/proj/JITtest$ clang -g -S -emit-llvm fn_lib.c
vub@vub:~/proj/JITtest$ clang++ -g jit_test.cpp -o jit_test `llvm-config
--cxxflags --ldflags --system-libs --libs all`
vub@vub:~/proj/JITtest$ ls
fn_lib.c  fn_lib.ll  jit_test  jit_test.cpp  ReadMe.txt
vub@vub:~/proj/JITtest$ ./jit_test

START!

parseIRFile

EngineBuilder create

Example: fn(7) = 5040

FINISH!
vub@vub:~/proj/JITtest$


Ubuntu 20, ARM64, clang-10


JITtest# lsb_release -a
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:focal
JITtest# clang++ -v
clang version 10.0.0-4ubuntu1
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/aarch64-linux-gnu/9
Found candidate GCC installation: /usr/lib/gcc/aarch64-linux-gnu/9
Selected GCC installation: /usr/bin/../lib/gcc/aarch64-linux-gnu/9
Candidate multilib: .;@m64
Selected multilib: .;@m64
JITtest# clang -v
clang version 10.0.0-4ubuntu1
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/aarch64-linux-gnu/9
Found candidate GCC installation: /usr/lib/gcc/aarch64-linux-gnu/9
Selected GCC installation: /usr/bin/../lib/gcc/aarch64-linux-gnu/9
Candidate multilib: .;@m64
Selected multilib: .;@m64
JITtest# ls
ReadMe.txt  fn_lib.c  jit_test.cpp
JITtest# clang -g -S -emit-llvm fn_lib.c
JITtest# clang++ -g jit_test.cpp -o jit_test `llvm-config --cxxflags --ldflags
--system-libs --libs all`
JITtest# ls
ReadMe.txt  fn_lib.c  fn_lib.ll  jit_test  jit_test.cpp
JITtest# ./jit_test

START!

parseIRFile

EngineBuilder create

Example: fn(7) = 5040

FINISH!
JITtest#


Ubuntu 20, x86_64, clang-12


vub@vub20c12:~/proj/JITtest$ lsb_release -a
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:focal
vub@vub20c12:~/proj/JITtest$ clang++-12 -v
Ubuntu clang version
12.0.0-++20210331122613+9ae9ab1ca343-1~exp1~20210330223318.69
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC i

[llvm-bugs] [Bug 50180] ObjFile feels a bit overtemplatized

2021-05-03 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=50180

Jez Ng  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)||https://github.com/llvm/llv
   ||m-project/commit/001ba65375
   ||f79a76491677cc2de05637f15a7
   ||a57

-- 
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