[llvm-bugs] [Bug 44891] New: Debugger can't access in-scope variables in OpenMP parallel regions

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44891

Bug ID: 44891
   Summary: Debugger can't access in-scope variables in OpenMP
parallel regions
   Product: OpenMP
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Clang Compiler Support
  Assignee: unassignedclangb...@nondot.org
  Reporter: kev...@redhat.com
CC: llvm-bugs@lists.llvm.org

Created attachment 23125
  --> https://bugs.llvm.org/attachment.cgi?id=23125&action=edit
Test case for in-scope variable openmp bug

Overview:

A debugger (either lldb or gdb) is unable to access certain in-scope variables
from within an OpenMP parallel region.  I've attached the test case that I've
written for GDB's test suite.  I could shortened this program for bug reporting
purposes, but ultimately it's worth considering each parallel region in this
file because each of these regions will likely show additional problems with
debugging in-scope variables.

I've tried clang 8 thru 10.0.0; each of these versions are broken.

In the examples below, s1, s3, and i3 are all in scope and should be printable
by the debugger, but are not.

I wanted to use clang 10.0.0 which is found in recent Fedora Rawhide.  These
same problems are also present on Fedora 31 and earlier which use earlier
versions of clang.

Steps to reproduce:

[kev@rawhide-1 tmp]$ clang --version
clang version 10.0.0 (Fedora 10.0.0-0.1.rc1.fc32)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
[kev@rawhide-1 tmp]$ clang -g -fopenmp -o omp-par-scope omp-par-scope.c
[kev@rawhide-1 tmp]$ lldb omp-par-scope
(lldb) target create "omp-par-scope"
Current executable set to '/tmp/omp-par-scope' (x86_64).
(lldb) b 39
Breakpoint 1: where = omp-par-scope`.omp_outlined._debug__ + 164 at
omp-par-scope.c:39:5, address = 0x00401354
(lldb) run
Process 599852 launched: '/tmp/omp-par-scope' (x86_64)
warning: (x86_64) /lib64/libarcher.so unsupported DW_FORM values: 0x1f20 0x1f21
Process 599852 stopped
* thread #2, name = 'omp-par-scope', stop reason = breakpoint 1.1
frame #0: 0x00401354
omp-par-scope`.omp_outlined._debug__(.global_tid.=0x7797cba0,
.bound_tid.=0x7797cb98, i1=0x7fffd61c) at omp-par-scope.c:39:5
   36   i2 = s2 + 10;
   37   
   38   #pragma omp critical
-> 39   printf ("single_scope: thread_num=%d, s1=%d, i1=%d, s2=%d,
i2=%d\n",
   40   thread_num, s1, i1, s2, i2);
   41 }
   42   
(lldb) p s1
error: :1:1: use of undeclared identifier 's1'
s1
^
(lldb) p s2
(int) $0 = 202
(lldb) p s3
error: :1:1: use of undeclared identifier 's3'
s3
^
(lldb) p i1
(int) $1 = 11
(lldb) p i2
(int) $2 = 212
(lldb) p i3
error: :1:1: use of undeclared identifier 'i3'
i3
^

GDB is able to print values for s1 and s3, but they are incorrect. (I haven't
investigated where they're coming from.)  Also note that gdb can't find a value
for i3.

[kev@rawhide-1 tmp]$ gdb -q omp-par-scope
Reading symbols from omp-par-scope...
(gdb) b 39
Breakpoint 1 at 0x401354: file omp-par-scope.c, line 39.
(gdb) run
Starting program: /tmp/omp-par-scope 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7797d780 (LWP 600272)]

Thread 1 "omp-par-scope" hit Breakpoint 1, .omp_outlined._debug__ (
.global_tid.=0x7fffd190, .bound_tid.=0x7fffd188, 
i1=@0x7fffd5ec: 11) at omp-par-scope.c:39
39  printf ("single_scope: thread_num=%d, s1=%d, i1=%d, s2=%d,
i2=%d\n",
(gdb) p s1
$1 = -3901428.39008634844799
(gdb) p s2
$2 = 102
(gdb) p s3
$3 = -3319055.88148504441733
(gdb) p i1
$4 = (int &) @0x7fffd5ec: 11
(gdb) p i2
$5 = 112
(gdb) p i3
No symbol "i3" in current context.
(gdb) 

Expected results:

Expected results can be found by compiling with gcc and then debugging with
gdb. (Though, at the moment, the value associated with i3 can only be found on
the master thread.  I am working on making it work for all threads.)

[kev@rawhide-1 tmp]$ gcc --version
gcc (GCC) 10.0.1 20200130 (Red Hat 10.0.1-0.7)
[...]
[kev@rawhide-1 tmp]$ gcc -g -fopenmp -o omp-par-scope omp-par-scope.c
[kev@rawhide-1 tmp]$ gdb -q omp-par-scope
Reading symbols from omp-par-scope...
(gdb) b 39
Breakpoint 1 at 0x40134e: file omp-par-scope.c, line 39.
(gdb) run
Starting program: /tmp/omp-par-scope 
Missing separate debuginfo for /lib64/libgomp.so.1
Try: dnf --enablerepo='*debug*' install
/usr/lib/debug/.build-id/ec/ae5692491ca61813e43a9988409c236a789a05.debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x77d6f700 (LWP 600426)]

Thread 1 "omp-par-scope" hit Breakpoint 1, single_scope._omp_fn.0 ()
at omp-par-scope.c:39
39  printf ("single_scope: thread_num=%d, s1=%d, i1=%d, s2=%d,
i2=%d\n",
(gdb) p s1
$1 = -41
(gdb) p s2
$2 = 102

[llvm-bugs] [Bug 44890] New: Clang fails to instantiate parent class with parameter pack

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44890

Bug ID: 44890
   Summary: Clang fails to instantiate parent class with parameter
pack
   Product: clang
   Version: 10.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: smee...@fb.com
CC: h...@chromium.org, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Blocks: 44555

$ cat reduced.cpp
template 
struct tuple {};

template 
int get0(const tuple& t) {
  return 0;
}

template 
struct tuple_wrapper : public tuple {
  template 
  int get() {
return get0<0, Ts...>(*this);
  }
};

int f() {
  tuple_wrapper w;
  return w.get<0>();
}

$ clang -cc1 -fsyntax-only reduced.cpp
reduced.cpp:13:12: error: no matching function for call to 'get0'
return get0<0, Ts...>(*this);
   ^~
reduced.cpp:19:12: note: in instantiation of function template specialization
'tuple_wrapper::get<0>' requested here
  return w.get<0>();
   ^
reduced.cpp:5:5: note: candidate template ignored: deduced type 'const tuple<>'
of 1st parameter does not match adjusted type 'tuple_wrapper' of argument
[with I = 0, Ts = <>]
int get0(const tuple& t) {
^
1 error generated.

I bisected this to
https://github.com/llvm/llvm-project/commit/907cefe721437fa8950c1b6c1c028038b175f921,
so it's a regression in 10.0. gcc, MSVC and Clang 9 all accept this code:
https://godbolt.org/z/TfZBf2

Clang trunk does compile this if I explicitly instantiate the parent class, but
I don't believe that should be necessary, i.e. if I change the body of
tuple_wrapper::get to

return get0<0, Ts...>(tuple(*this));


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 44560] OpenMP IRBuilder passes invalid DISubprogram to CodeExtractor

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44560

Johannes Doerfert  changed:

   What|Removed |Added

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

--- Comment #3 from Johannes Doerfert  ---
Fixed in 8a56d64d7620b3764f10f03f3a1e307fcdd72c2f

-- 
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 44889] New: LoopRotate compile-time regression due to MemorySSA

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44889

Bug ID: 44889
   Summary: LoopRotate compile-time regression due to MemorySSA
   Product: libraries
   Version: 10.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: nikita@gmail.com
CC: alina.sbir...@gmail.com, llvm-bugs@lists.llvm.org
Blocks: 44555

Created attachment 23123
  --> https://bugs.llvm.org/attachment.cgi?id=23123&action=edit
Large bitcode test case

Running the given test-case through opt -O3 gives the following timings for
loop rotation passes:

   0.4672 (  5.1%)   0.0079 (  1.4%)   0.4751 (  4.9%)   0.4750 (  4.9%) 
Rotate Loops #2
   0.1104 (  1.2%)   0.0052 (  0.9%)   0.1156 (  1.2%)   0.1155 (  1.2%) 
Rotate Loops

With with opt -O3 -enable-mssa-loop-dependency=0 we get:

   0.0944 (  0.9%)   0.0037 (  0.7%)   0.0981 (  0.9%)   0.0980 (  0.9%) 
Rotate Loops #2
   0.0394 (  0.4%)   0.0017 (  0.3%)   0.0411 (  0.4%)   0.0409 (  0.4%) 
Rotate Loops

That is, loop rotation has become 5x more expensive with MemorySSA enabled.
Presumably updating MemorySSA during loop rotation is very expensive.

This is one of the large compile-time regressions we've observed when trying to
upgrade to LLVM 10 in rust. You can see the full impact of enabling MemorySSA
(all else being equal) on end-to-end compile times at
https://perf.rust-lang.org/compare.html?start=9993408439c871c1bc0c0bac3b3008b24039443c&end=52e999afd3be3341463f3b87be02f2bcfb381c17.


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 44888] New: "Clang - Getting Started" page says to use makefiles

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44888

Bug ID: 44888
   Summary: "Clang - Getting Started" page says to use makefiles
   Product: Documentation
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: General docs
  Assignee: unassignedb...@nondot.org
  Reporter: nbill...@google.com
CC: llvm-bugs@lists.llvm.org

The instructions for building clang (on Linux) at
https://clang.llvm.org/get_started.html say to configure cmake with "cmake
-DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm" and then to build
with "make".

This method of building is extremely slow compared with building with ninja. I
tried to follow these instructions naively and the build was so slow that,
after waiting about an hour it still self-reported about 12% progress. After
running "cmake -DLLVM_ENABLE_PROJECTS=clang -G Ninja ../llvm", and then
building with ninja, the entire build took at most 15 minutes.

Is it possible to at least describe both configurations so that readers don't
have to find and fix the issues with make on their own?

-- 
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 44887] New: function attributes weak and alias undocumented

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44887

Bug ID: 44887
   Summary: function attributes weak and alias undocumented
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Documentation
  Assignee: unassignedclangb...@nondot.org
  Reporter: ndesaulni...@google.com
CC: llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk,
srhi...@google.com

https://clang.llvm.org/docs/AttributeReference.html doesn't seem to document
"weak" or "alias" function attributes.

https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/Function-Attributes.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 44853] -mno-save-restore spams a RISCV Linux kernel build

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44853

Nathan Chancellor  changed:

   What|Removed |Added

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

--- Comment #4 from Nathan Chancellor  ---
Yes, these warnings are gone with my version of clang at
bc316c21570b3ff93a7e064a6fb2f6b56d26d850, I'll close this, thank you!

-- 
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 44886] New: Bitfields in class templates cause assertion failures

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44886

Bug ID: 44886
   Summary: Bitfields in class templates cause assertion failures
   Product: clang
   Version: 10.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: smee...@fb.com
CC: elizabeth.andr...@intel.com, h...@chromium.org,
llvm-bugs@lists.llvm.org, melanie.blo...@intel.com,
neeil...@live.com, richard-l...@metafoo.co.uk
Blocks: 44555

$ cat reduced.cpp
template  class C {
  enum { K = 1 };
  int i : K;
  unsigned u() { return i; }
};

$ clang -cc1 -fsyntax-only reduced.cpp
clang: /home/smeenai/llvm-project/clang/lib/AST/ExprConstant.cpp:14529: bool
clang::Expr::isIntegerConstantExpr(llvm::APSInt &, const clang::ASTContext &,
clang::SourceLocation *, bool) const: Assertion `!isValueDependent() &&
"Expression evaluator can't be called on a de
pendent expression."' failed.

I bisected this to
https://github.com/llvm/llvm-project/commit/878a24ee244a24c39d1c57e9af2e88c621f7cce9,
so it's a regression from 9 to 10.


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 27036] InstCombine: (float) x + (float) y -> (float) (x + y) incorrect

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=27036

Ehud Katz  changed:

   What|Removed |Added

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

--- Comment #4 from Ehud Katz  ---
Fixed in LLVM 5.0

-- 
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 16239 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::report_fatal_error

2020-02-12 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #3 on issue 16239 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: 
Unexpected-exit in llvm::report_fatal_error
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16239#c3

ClusterFuzz testcase 5715272618475520 is verified as fixed in 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202002110531:202002120539

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] Issue 16246 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::report_fatal_error

2020-02-12 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #3 on issue 16246 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: 
Unexpected-exit in llvm::report_fatal_error
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16246#c3

ClusterFuzz testcase 5195086714896384 is verified as fixed in 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202002110531:202002120539

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 44555] [meta] 10.0.0 Release Blockers

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

Bug 44877 Summary: [CodeGenPrepare] Store splitting creates invalid alignments 
on big-endian targets, and under-aligned stores on all targets
https://bugs.llvm.org/show_bug.cgi?id=44877

   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 44877] [CodeGenPrepare] Store splitting creates invalid alignments on big-endian targets, and under-aligned stores on all targets

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44877

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #6 from Hans Wennborg  ---
(In reply to Clement Courbet from comment #5)
> Created attachment 23122 [details]
> cherry-pick of rG15488ff24b4a on top of 10

Thanks! Pushed that as b3cf70427eb1e97d9b89ba6e9298c280c8a32c74

-- 
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 44822] Assertion failure in Parser.h:941: !isActive && "Forgot to call Commit or Revert!" when using concepts

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44822

Saar Raz  changed:

   What|Removed |Added

 CC||saar@raz.email
 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)||271e495399170d69627c1acd591
   ||c9298cb0b5b4b

-- 
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 44666] Assertion failure when using concepts combined with variadic templates and overload resolution

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44666

Saar Raz  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #1 from Saar Raz  ---
This doesn't crash anymore, probably fixed by earlier commits.

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44714, which changed state.

Bug 44714 Summary: [CodeComplete][Concepts] Crash finding overloads of 
constrained auto function
https://bugs.llvm.org/show_bug.cgi?id=44714

   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 44714] [CodeComplete][Concepts] Crash finding overloads of constrained auto function

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44714

Saar Raz  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||saar@raz.email
 Status|NEW |RESOLVED
 Fixed By Commit(s)||5fef14d932fe602bf998b8fb8a8
   ||09ff85ca1e245

--- Comment #2 from Saar Raz  ---
Hey,
I do have a bugzilla account 😅
Are there any other concepts bugs you encountered?

-- 
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 44589] _mm_extract_pi16 and _mm_insert_pi16 warn with -Wvector-conversion

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44589

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #3 from Hans Wennborg  ---
Cherry-picked to 10.x as 533d98bdced6f75d0c7e4f42476b3bc873a113b6

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44589, which changed state.

Bug 44589 Summary: _mm_extract_pi16 and _mm_insert_pi16 warn with 
-Wvector-conversion
https://bugs.llvm.org/show_bug.cgi?id=44589

   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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 39413, which changed state.

Bug 39413 Summary: GlobalMerge optimization drops ELF visibility attributes
https://bugs.llvm.org/show_bug.cgi?id=39413

   What|Removed |Added

 Status|CONFIRMED   |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 39413] GlobalMerge optimization drops ELF visibility attributes

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39413

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #2 from Hans Wennborg  ---
(In reply to Michael Spang from comment #1)
> https://reviews.llvm.org/D73235

That landed in

a2fb2c0ddca14c133f24d08af4a78b6a3d612ec6

with a test fix follow-up in

6be9acdfa814dee6c57833d5351137c72c11fbd3


Those were then merged to 10.x in
425198bf1f98e93be37b8675e29ac6d37529dc68
and 1f95a775949e75b4cac48a0fb4e443e6725e9b64

-- 
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 44884] New: Debug information shows incorrect lexical scope for typedef.

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44884

Bug ID: 44884
   Summary: Debug information shows incorrect lexical scope for
typedef.
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: DebugInfo
  Assignee: unassignedb...@nondot.org
  Reporter: international.phan...@gmail.com
CC: jdevliegh...@apple.com, keith.wal...@arm.com,
llvm-bugs@lists.llvm.org,
paul_robin...@playstation.sony.com

Given the following test case:

//
// typedef.cpp
//

int bar(float Input) { return (int)Input; }

unsigned foo(char Param) {
  typedef int INT;
  INT Value = Param;
  {
typedef float FLOAT;
{
  FLOAT Added = Value + Param;
  Value = bar(Added);
}
  }
  return Value + Param;
}

//

Using the following command line options to generate debug info
(DWARF) and (COFF):

clang -c -g -O0 typedef.cpp -o typedef.o
clang -c -g -O0 typedef.cpp -o typedef-coff.o -gcodeview
--target=x86_64-windows

Looking at the output generated by llvm-dwarfdump and llvm-diva,
the debug info shows the typedefs 'INT'and 'FLOAT' to be at the same lexical
scope (function scope).

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44882, which changed state.

Bug 44882 Summary: Please cherry-pick two debuginfo reverts into the release-10 
branch
https://bugs.llvm.org/show_bug.cgi?id=44882

   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 44882] Please cherry-pick two debuginfo reverts into the release-10 branch

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44882

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #1 from Hans Wennborg  ---
(In reply to Jeremy Morse from comment #0)
> Hi Hans,
> 
> Could you please cherry pick these two commits into the release-10 branch:
> 
>   rGece761427f63de96ee52bbd6be1c61b07967a917

Cherry-picked as 04d7337d69fa38f00179811419207a9ef5eef83e

>   rG6531a78ac4b5b229bce272706593a0bc873877d7

and 4eb45a05a78f7c80bbec0453bc225deebec06209.

Thanks!

-- 
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 44882] Please cherry-pick two debuginfo reverts into the release-10 branch

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44882
Bug 44882 depends on bug 44814, which changed state.

Bug 44814 Summary: Please cherry-pick rG41206b61e30c into the release-10 branch
https://bugs.llvm.org/show_bug.cgi?id=44814

   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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44814, which changed state.

Bug 44814 Summary: Please cherry-pick rG41206b61e30c into the release-10 branch
https://bugs.llvm.org/show_bug.cgi?id=44814

   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 44814] Please cherry-pick rG41206b61e30c into the release-10 branch

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44814

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #1 from Hans Wennborg  ---
Cherry-picked to 10.x as c1701728b93b3aec39d3b93d0182648887edfdb1

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44816, which changed state.

Bug 44816 Summary: bugprone-infinite-loop false positive with CATCH2
https://bugs.llvm.org/show_bug.cgi?id=44816

   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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 39674, which changed state.

Bug 39674 Summary: [C++] ICE on the nested pointer indirection with address 
space conversion
https://bugs.llvm.org/show_bug.cgi?id=39674

   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 39674] [C++] ICE on the nested pointer indirection with address space conversion

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39674

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #6 from Hans Wennborg  ---
(In reply to Anastasia Stulova from comment #5)
> @hans, is it still possible to merge
> https://reviews.llvm.org/rG6064f426a18304e16b51cc79e74c9c2d55ef5a9c in
> release 10 branch?

Yes. Pushed to 10.x as b33830aea54536f0f03334b2015b03af336ec90c.

-- 
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 20657 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Unexpected-exit in llvm::sys::Process::Exit

2020-02-12 Thread ClusterFuzz-External via monorail via llvm-bugs
Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, 
igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, 
eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, 
v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com 
Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-llvm 
Reported-2020-02-12
Type: Bug

New issue 20657 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: 
Unexpected-exit in llvm::sys::Process::Exit
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20657

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

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

Crash Type: Unexpected-exit
Crash Address: 
Crash State:
  llvm::sys::Process::Exit
  llvm::report_fatal_error
  llvm::report_fatal_error
  
Sanitizer: address (ASAN)

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

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

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 44883] New: Losing a global const int in clang++

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44883

Bug ID: 44883
   Summary: Losing a global const int in clang++
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: felix-l...@fefe.de
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

I'm having a bizarre issue that I suspect is my fault, but I am running out of
ideas on why. Sorry for wasting your time but can you please explain this to
me:

  $ cat a.cc
  const int foo = 23;
  $ cat b.cc
  extern const int foo;
  int main() { return foo; }
  $

First issue:

  $ nm b.o
   U foo
   T main
  $

OK I see why main is not mangled. But foo should be mangled, no?
Doing extern "C++" const int foo does not help, still not mangled.

Second issue:

  $ nm a.o
  $

Nothing. What happened to foo?
Renaming the files to a.c and b.c makes things work.
Have I missed a C++ memo or two here?

I tried this with GCC too, and g++ will generate a mangled foo symbol in a.o
(_ZL3foo) but it will generate a reference to unmangled foo in b.o. I filed a
bug with them, too.

-- 
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 44882] New: Please cherry-pick two debuginfo reverts into the release-10 branch

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44882

Bug ID: 44882
   Summary: Please cherry-pick two debuginfo reverts into the
release-10 branch
   Product: libraries
   Version: 10.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Common Code Generator Code
  Assignee: unassignedb...@nondot.org
  Reporter: jeremy.morse.l...@gmail.com
CC: llvm-bugs@lists.llvm.org
Depends on: 44814
Blocks: 44555

Hi Hans,

Could you please cherry pick these two commits into the release-10 branch:

  rGece761427f63de96ee52bbd6be1c61b07967a917
  rG6531a78ac4b5b229bce272706593a0bc873877d7

They're reverts of the work in https://reviews.llvm.org/D68945 that turned out
to be half baked, and breaks debug information for -fsanitize=safe-stack, as
reported in bug 44585. Crucially, incorrect locations under safestack are being
generated even at -O0, which is a fairly bad failure.

For a clean merge, these commits depend on the cherry pick in bug 44814. This
is due to a spurious test conflict; I can separate the two if needs be.

Thanks for all the release engineering!


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=44555
[Bug 44555] [meta] 10.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=44814
[Bug 44814] Please cherry-pick rG41206b61e30c into the release-10 branch
-- 
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 38768] [meta][DebugInfo] Umbrella bug for poor debug experiences

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=38768
Bug 38768 depends on bug 39724, which changed state.

Bug 39724 Summary: [DebugInfo] Arguments are lost after a call across TUs
https://bugs.llvm.org/show_bug.cgi?id=39724

   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 39724] [DebugInfo] Arguments are lost after a call across TUs

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39724

Jeremy Morse  changed:

   What|Removed |Added

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

--- Comment #6 from Jeremy Morse  ---
Salvaging spun into bug 44881, the more general problem was solved by
entry-value variable locations, many thanks all!

-- 
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 44881] New: [DebugInfo@O2] DAGCombine drops easily salvageable variable location

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44881

Bug ID: 44881
   Summary: [DebugInfo@O2] DAGCombine drops easily salvageable
variable location
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Keywords: wrong-debug
  Severity: normal
  Priority: P
 Component: Common Code Generator Code
  Assignee: unassignedb...@nondot.org
  Reporter: jeremy.morse.l...@gmail.com
CC: chackz0...@gmail.com, greg.bedw...@sony.com,
llvm-bugs@lists.llvm.org, orlando.hy...@sony.com,
paul.robin...@am.sony.com, stephen.to...@sony.com,
v...@apple.com
Blocks: 38768

Spun off from bug 39724, Davides test case which I copy below has 'l' optimised
out in the fn1 function. The cause appears to be a DAGCombine that drops the
multiply, which the SelectionDAG salvager can't recover. This is true of todays
master, 2733ad2c24 ish.

8<
a.c:

extern void other_func(long int, long int, long int);

__attribute__((noinline))
int fn1 (long int x, long int y, long int z) {
int l = x * 2;
int q = y * z;
other_func(x, y, z);
return l + q;
}

__attribute__((noinline)) long int
fn2 (long int a, long int b, long int c)
{
  long int q = 2 * a;
return fn1 (5, 6, 7);
}

int main(void) {
return fn2(14, 23, 34);
}

b.c:

void other_func(long int a, long int b, long int c) {}


built with: ${CC} a.c b.c -O3 -g
>8

I guess this ticket can more broadly represents the fact that all the folding /
morphing in DAGCombine isn't robustly salvaged.


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=38768
[Bug 38768] [meta][DebugInfo] Umbrella bug for poor debug experiences
-- 
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 44880] New: Debug invariance in GlobalOpt

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44880

Bug ID: 44880
   Summary: Debug invariance in GlobalOpt
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: DebugInfo
  Assignee: unassignedb...@nondot.org
  Reporter: david.stenb...@ericsson.com
CC: jdevliegh...@apple.com, keith.wal...@arm.com,
llvm-bugs@lists.llvm.org,
paul_robin...@playstation.sony.com

Created attachment 23121
  --> https://bugs.llvm.org/attachment.cgi?id=23121&action=edit
IR reproducer.

After the introduction of "[InstCombine][DebugInfo] Fold constants wrapped in
metadata", some debug invariance started appearing.

Please note that that commit was reverted in
982944525c7706c4dee00042d5b7cf2f0d87804f due to this issue.

C reproducer:

int a, b, c;
static int arr[4];

void foo() {
  const int *e[] = {&arr[2]};
  const int **f = &e[0];
  c = f != foo;
}

int main() {
  for (b = 0; b < 4; b++)
a = a ^ arr[b];
  return 0;
}

Commands:

$ clang -O3 -g globalopt.c -S -o - -mllvm -disable-debug-info-print -o
with-debug.s
$ clang -O3 globalopt.c -S -o - -mllvm -disable-debug-info-print -o
without-debug.s
$ diff -u without-debug.s with-debug.s
[...]
+   movlarr(%rip), %eax
+   xorla(%rip), %eax
+   xorlarr+4(%rip), %eax
+   xorlarr+8(%rip), %eax
+   xorlarr+12(%rip), %eax
+   movl%eax, a(%rip)
movl$4, b(%rip)
xorl%eax, %eax
retq

That commit appears to have exposed a pre-existing debug invariance issue in
GlobalOpt.

This can also be reproduced by just running GlobalOpt on the attached IR
reproducer.

$ opt -strip-debug globalopt.ll | opt -S -globalopt -o without-debug.ll
$ opt globalopt.ll | opt -S -globalopt -strip-debug -o with-debug.ll
$ diff without-debug.ll with-debug.ll
[...]
-  %xor = xor i32 0, %a.promoted
-  %xor.1 = xor i32 0, %xor
-  %xor.2 = xor i32 0, %xor.1
-  %xor.3 = xor i32 0, %xor.2
+  %0 = load i32, i32* getelementptr inbounds ([4 x i32], [4 x i32]* @arr,
i64 0, i64 0), align 16
+  %xor = xor i32 %0, %a.promoted
+  %1 = load i32, i32* getelementptr inbounds ([4 x i32], [4 x i32]* @arr,
i64 0, i64 1), align 4
+  %xor.1 = xor i32 %1, %xor
+  %2 = load i32, i32* getelementptr inbounds ([4 x i32], [4 x i32]* @arr,
i64 0, i64 2), align 8
+  %xor.2 = xor i32 %2, %xor.1
+  %3 = load i32, i32* getelementptr inbounds ([4 x i32], [4 x i32]* @arr,
i64 0, i64 3), align 4
+  %xor.3 = xor i32 %3, %xor.2

The issue seems to be that the dbg.value intrinsic:

  call void @llvm.dbg.value(metadata i64 ptrtoint (i32* getelementptr inbounds
([4 x i32], [4 x i32]* @arr, i64 0, i64 2) to i64), metadata !24, metadata
!DIExpression()), !dbg !32

seems to lead to GlobalStatus::analyzeGlobal() returning true that @arr has its
address taken. This seems to have to do with the analysis bailing out due to
the ptrtoint use of the GEP:

  // If the result of the constantexpr isn't pointer type, then we won't
  // know to expect it in various places.  Just reject early.
  if (!isa(CE->getType()))
return true;

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44877, which changed state.

Bug 44877 Summary: [CodeGenPrepare] Store splitting creates invalid alignments 
on big-endian targets, and under-aligned stores on all targets
https://bugs.llvm.org/show_bug.cgi?id=44877

   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 44877] [CodeGenPrepare] Store splitting creates invalid alignments on big-endian targets, and under-aligned stores on all targets

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44877

Roman Lebedev  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Blocks||44555
 Status|RESOLVED|REOPENED


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 42861] Regression 9.0.0-RC1 Assertion failed: (!E || isa(E)) && "missing non-odr-use marking for unevaluated decl ref",

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=42861

Richard Smith  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|REOPENED

--- Comment #4 from Richard Smith  ---
Still failing after PR43080 was fixed. Reduced target-independent testcase:

namespace std { struct type_info; }
struct A { virtual ~A(); };
void f(const A &t) { [&t](auto) { typeid(t); }(0); }

-- 
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 42474] [meta] 9.0.0 Release Blockers

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=42474
Bug 42474 depends on bug 42861, which changed state.

Bug 42861 Summary: Regression 9.0.0-RC1 Assertion failed: (!E || 
isa(E)) && "missing non-odr-use marking for unevaluated 
decl ref",
https://bugs.llvm.org/show_bug.cgi?id=42861

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

-- 
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 44877] [CodeGenPrepare] Store splitting creates invalid alignments on big-endian targets, and under-aligned stores on all targets

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44877

Clement Courbet  changed:

   What|Removed |Added

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

--- Comment #2 from Clement Courbet  ---
Fixed by rG15488ff24b4a

-- 
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 44851] [CodeGenPrepare] Assertion `Lhs != 1 && "Can't halve byte alignment"' failed.

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44851

Clement Courbet  changed:

   What|Removed |Added

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

--- Comment #2 from Clement Courbet  ---
Fixed by rG15488ff24b4a

-- 
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 44849] llvm 10 rc1 fails to build on s390x - stage2 build

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44849

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #6 from Hans Wennborg  ---
Cherry-picked to 10.x in 3c94b2780126be9cf0e828bbd62729cdc5f421da

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44849, which changed state.

Bug 44849 Summary: llvm 10 rc1 fails to build on s390x - stage2 build
https://bugs.llvm.org/show_bug.cgi?id=44849

   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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44705, which changed state.

Bug 44705 Summary: report_fatal_error no longer generates preprocessed source + 
reproducer.sh
https://bugs.llvm.org/show_bug.cgi?id=44705

   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 44705] report_fatal_error no longer generates preprocessed source + reproducer.sh

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44705

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #7 from Hans Wennborg  ---
(In reply to Luke from comment #6)
> Reopening for 10.0 backport.
> 
> https://github.com/llvm/llvm-project/commit/
> faace365088a2a3a4cb1050a9facfc34a7a56577

Pushed to 10.x as fd04cb43e1d83c6f18c932de94c1e341272ed160

-- 
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 3359] fmod in APFloat is badly broken

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=3359

Ehud Katz  changed:

   What|Removed |Added

 Fixed By Commit(s)||rG9d0956ebd471
 Status|CONFIRMED   |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 44878] New: crash with --emit-relocs and --strip-debug when debug sections present

2020-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44878

Bug ID: 44878
   Summary: crash with --emit-relocs and --strip-debug when debug
sections present
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: keesc...@chromium.org
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org

Combining --emit-relocs with --strip-debug on an object with debug sections
will crash during orphan placement:

$ echo "a;" > test.c
$ clang -g -c -o test.o test.c
...
$ objdump -wh test.o

test.o: file format elf64-x86-64

Sections:
Idx NameSize  VMA   LMA   File off 
Algn  Flags
  0 .text         0040 
2**2  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .debug_str  0091      0040 
2**0  CONTENTS, READONLY, DEBUGGING
  2 .debug_abbrev   002c      00d1 
2**0  CONTENTS, READONLY, DEBUGGING
  3 .debug_info 003b      00fd 
2**0  CONTENTS, RELOC, READONLY, DEBUGGING
  4 .comment006a      0138 
2**0  CONTENTS, READONLY
  5 .note.GNU-stack       01a2 
2**0  CONTENTS, READONLY
  6 .debug_line 002e      01a2 
2**0  CONTENTS, READONLY, DEBUGGING
  7 .llvm_addrsig         0320 
2**0  CONTENTS, READONLY, EXCLUDE

$ ld.lld --emit-relocs --strip-debug -o /dev/null test.o
Stack dump:
0.  Program arguments: ld.lld --emit-relocs --strip-debug -o /dev/null
test.o 
 #0 0x55a6d904b68e llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/home/kees/src/llvm-build/x86/bin/lld+0x51168e)
 #1 0x55a6d9049514 llvm::sys::RunSignalHandlers()
(/home/kees/src/llvm-build/x86/bin/lld+0x50f514)
 #2 0x55a6d9049658 SignalHandler(int)
(/home/kees/src/llvm-build/x86/bin/lld+0x50f658)
 #3 0x7fe35d416540 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x15540)
 #4 0x55a6d9028122 llvm::Twine::printOneChild(llvm::raw_ostream&,
llvm::Twine::Child, llvm::Twine::NodeKind) const
(/home/kees/src/llvm-build/x86/bin/lld+0x4ee122)
 #5 0x55a6d90282a1 llvm::Twine::toVector(llvm::SmallVectorImpl&)
const (/home/kees/src/llvm-build/x86/bin/lld+0x4ee2a1)
 #6 0x55a6d902834b llvm::Twine::str[abi:cxx11]() const
(/home/kees/src/llvm-build/x86/bin/lld+0x4ee34b)
 #7 0x55a6d9261a9f
lld::elf::getOutputSectionName(lld::elf::InputSectionBase const*)
(/home/kees/src/llvm-build/x86/bin/lld+0x727a9f)
 #8 0x55a6d91a8a5e
lld::elf::LinkerScript::addOrphanSections()::'lambda'(lld::elf::InputSectionBase*)::operator()(lld::elf::InputSectionBase*)
const (/home/kees/src/llvm-build/x86/bin/lld+0x66ea5e)
 #9 0x55a6d91a6177 lld::elf::LinkerScript::addOrphanSections()
(/home/kees/src/llvm-build/x86/bin/lld+0x66c177)
#10 0x55a6d912ce0e void
lld::elf::LinkerDriver::link >(llvm::opt::InputArgList&)
(/home/kees/src/llvm-build/x86/bin/lld+0x5f2e0e)
#11 0x55a6d8f7c833 lld::elf::LinkerDriver::main(llvm::ArrayRef) (/home/kees/src/llvm-build/x86/bin/lld+0x442833)
#12 0x55a6d9130dfb lld::elf::link(llvm::ArrayRef, bool,
llvm::raw_ostream&, llvm::raw_ostream&)
(/home/kees/src/llvm-build/x86/bin/lld+0x5f6dfb)
#13 0x55a6d8f79ede main (/home/kees/src/llvm-build/x86/bin/lld+0x43fede)
#14 0x7fe35ce921e3 __libc_start_main
/build/glibc-4WA41p/glibc-2.30/csu/../csu/libc-start.c:342:3
#15 0x55a6d900aa4e _start (/home/kees/src/llvm-build/x86/bin/lld+0x4d0a4e)
Segmentation fault (core dumped)

-- 
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-02-12 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=44555
Bug 44555 depends on bug 44816, which changed state.

Bug 44816 Summary: bugprone-infinite-loop false positive with CATCH2
https://bugs.llvm.org/show_bug.cgi?id=44816

   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