[llvm-bugs] [Bug 45355] New: opt -simple-loop-unswitch crashing with Assertion `llvm::find(Res, Child) == Res.end() && "Unexpected child found in the CFG"' failed.

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45355

Bug ID: 45355
   Summary: opt -simple-loop-unswitch crashing with Assertion
`llvm::find(Res, Child) == Res.end() && "Unexpected
child found in the CFG"' failed.
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: mikael.hol...@ericsson.com
CC: llvm-bugs@lists.llvm.org

Created attachment 23293
  --> https://bugs.llvm.org/attachment.cgi?id=23293&action=edit
bbi-40855_2.ll reproducer

Reproduce with:
 opt -S -o - bbi-40855_2.ll -simple-loop-unswitch 

Result:

opt: ../include/llvm/Support/GenericDomTreeConstruction.h:160: static
llvm::DomTreeBuilder::SemiNCAInfo::ChildrenGetter::ResultTy
llvm::DomTreeBuilder::SemiNCAInfo
>::ChildrenGetter::Get(llvm::DomTreeBuilder::SemiNCAInfo::NodePtr,
llvm::DomTreeBuilder::SemiNCAInfo::BatchUpdatePtr) [DomTreeT =
llvm::DominatorTreeBase, Inverse = false]: Assertion
`llvm::find(Res, Child) == Res.end() && "Unexpected child found in the CFG"'
failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace.
Stack dump:
0.  Program arguments: ../../master/llvm/build-all-builtins/bin/opt -S -o -
bbi-40855_2.ll -simple-loop-unswitch 
1.  Running pass 'Function Pass Manager' on module 'bbi-40855_2.ll'.
2.  Running pass 'Loop Pass Manager' on function '@f'
3.  Running pass 'Simple unswitch loops' on basic block '%for.cond1'
 #0 0x0429aa64 PrintStackTraceSignalHandler(void*)
(../../master/llvm/build-all-builtins/bin/opt+0x429aa64)
 #1 0x0429862e llvm::sys::RunSignalHandlers()
(../../master/llvm/build-all-builtins/bin/opt+0x429862e)
 #2 0x0429ae6c SignalHandler(int)
(../../master/llvm/build-all-builtins/bin/opt+0x429ae6c)
 #3 0x7f62ef76c890 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
 #4 0x7f62ee215e97 raise
/build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51:0
 #5 0x7f62ee217801 abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:81:0
 #6 0x7f62ee20739a __assert_fail_base
/build/glibc-OTsEL5/glibc-2.27/assert/assert.c:89:0
 #7 0x7f62ee207412 (/lib/x86_64-linux-gnu/libc.so.6+0x30412)
 #8 0x03a8fbf4
llvm::DomTreeBuilder::SemiNCAInfo >::ChildrenGetter::Get(llvm::BasicBlock*,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo*)
(../../master/llvm/build-all-builtins/bin/opt+0x3a8fbf4)
 #9 0x03a8645c
llvm::DomTreeBuilder::SemiNCAInfo >::DeleteEdge(llvm::DominatorTreeBase&,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo*, llvm::BasicBlock*, llvm::BasicBlock*)
(../../master/llvm/build-all-builtins/bin/opt+0x3a8645c)
#10 0x03aa1a6c
llvm::DomTreeBuilder::SemiNCAInfo >::ApplyNextUpdate(llvm::DominatorTreeBase&,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo&)
(../../master/llvm/build-all-builtins/bin/opt+0x3aa1a6c)
#11 0x03a8765b
llvm::DomTreeBuilder::SemiNCAInfo >::ApplyUpdates(llvm::DominatorTreeBase&,
llvm::ArrayRef >)
(../../master/llvm/build-all-builtins/bin/opt+0x3a8765b)
#12 0x04190c2f unswitchAllTrivialConditions(llvm::Loop&,
llvm::DominatorTree&, llvm::LoopInfo&, llvm::ScalarEvolution*,
llvm::MemorySSAUpdater*)
(../../master/llvm/build-all-builtins/bin/opt+0x4190c2f)
#13 0x041ab169 (anonymous
namespace)::SimpleLoopUnswitchLegacyPass::runOnLoop(llvm::Loop*,
llvm::LPPassManager&) (../../master/llvm/build-all-builtins/bin/opt+0x41ab169)
#14 0x0344bddb llvm::LPPassManager::runOnFunction(llvm::Function&)
(../../master/llvm/build-all-builtins/bin/opt+0x344bddb)
#15 0x03af5374 llvm::FPPassManager::runOnFunction(llvm::Function&)
(../../master/llvm/build-all-builtins/bin/opt+0x3af5374)
#16 0x03af5628 llvm::FPPassManager::runOnModule(llvm::Module&)
(../../master/llvm/build-all-builtins/bin/opt+0x3af5628)
#17 0x03af5c7d llvm::legacy::PassManagerImpl::run(llvm::Module&)
(../../master/llvm/build-all-builtins/bin/opt+0x3af5c7d)
#18 0x02370d9f main
(../../master/llvm/build-all-builtins/bin/opt+0x2370d9f)
#19 0x7f62ee1f8b97 __libc_start_main
/build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:344:0
#20 0x0235b02a _start
(../../master/llvm/build-all-builtins/bin/opt+0x235b02a)
Abort (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 40720] [AVX] extracting high 128 and zero-extending to 256 pessimized from vextracti128 to vperm2f128, even with -march=znver1

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=40720

Simon Pilgrim  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)||rG7734e4b3a36f,rG9c8ec99c80
   ||a5,rGe95d04f4f19d

--- Comment #1 from Simon Pilgrim  ---
Fixed in trunk

rG7734e4b3a36f - handles 256-bit AVX1/AVX2 cases
rG9c8ec99c80a5/rGe95d04f4f19d - handles 512-bit AVX512 cases

-- 
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 22897] Make codegen tests more robust

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=22897

Simon Pilgrim  changed:

   What|Removed |Added

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

--- Comment #12 from Simon Pilgrim  ---
I think we can resolve this - the update checks scripts have been actively used
for years now and a high proportion of the x86 codegen tests have been
regenerated.

-- 
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 45357] New: clang-format: unexpected change on operator

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45357

Bug ID: 45357
   Summary: clang-format: unexpected change on operator
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Keywords: regression
  Severity: normal
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: sylves...@debian.org
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Depends on: 45309

with:
class UniquePtrGetterAddRefs {
  operator void **() { return reinterpret_cast(&mPtrStorage); }
}

with clang-format 10.0

$ clang-format-10 foo.cpp 
class UniquePtrGetterAddRefs {
  operator void * *() { return reinterpret_cast(&mPtrStorage); }
}

I don't think it is what we want!


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=45309
[Bug 45309] [meta] 10.0.1 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 45358] New: clang-format: unexpected change on template declaration

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45358

Bug ID: 45358
   Summary: clang-format: unexpected change on template
declaration
   Product: clang
   Version: 10.0
  Hardware: PC
OS: Linux
Status: NEW
  Keywords: regression
  Severity: normal
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: sylves...@debian.org
CC: djas...@google.com, dma...@mozilla.com,
kli...@google.com, llvm-bugs@lists.llvm.org,
unassignedclangb...@nondot.org
Blocks: 45309, 36294

with:
template 
BaseAutoUnlock(MutexType &)->BaseAutoUnlock;


clang-format-10 returns:
template 
BaseAutoUnlock(MutexType &) -> BaseAutoUnlock;

(note the " -> ")

not sure it is a legit change?


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=36294
[Bug 36294] AlwaysBreakAfterReturnType works incorrectly for some operator
functions
https://bugs.llvm.org/show_bug.cgi?id=45309
[Bug 45309] [meta] 10.0.1 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 36294] AlwaysBreakAfterReturnType works incorrectly for some operator functions

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=36294
Bug 36294 depends on bug 45358, which changed state.

Bug 45358 Summary: clang-format: unexpected change on template declaration
https://bugs.llvm.org/show_bug.cgi?id=45358

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
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 45309] [meta] 10.0.1 Release Blockers

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45309
Bug 45309 depends on bug 45358, which changed state.

Bug 45358 Summary: clang-format: unexpected change on template declaration
https://bugs.llvm.org/show_bug.cgi?id=45358

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
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 45358] clang-format: unexpected change on template declaration

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45358

David Major  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from David Major  ---
This appears to be intentional per bug 35518.

-- 
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 45080] Wrong debug info generated at -O3 (-O0 is correct)

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45080

Chris Jackson  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Chris Jackson  ---
Committed upstream at
https://github.com/llvm/llvm-project/commit/135709aa9013565b9d02000bb0ca744f7585e6a5

-- 
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-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=38768
Bug 38768 depends on bug 45080, which changed state.

Bug 45080 Summary: Wrong debug info generated at -O3 (-O0 is correct)
https://bugs.llvm.org/show_bug.cgi?id=45080

   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 38768] [meta][DebugInfo] Umbrella bug for poor debug experiences

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

Bug 44371 Summary: Wrong debug info generated at -O3 (-O0 is correct)
https://bugs.llvm.org/show_bug.cgi?id=44371

   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 44371] Wrong debug info generated at -O3 (-O0 is correct)

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=44371

Chris Jackson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Chris Jackson  ---
Fix committed upstream at
https://github.com/llvm/llvm-project/commit/f6b2c003f360c3d0dcfe13d751805643f229f79b

-- 
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 45360] New: wrong code at -O2 on x86_64-linux-gnu

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45360

Bug ID: 45360
   Summary: wrong code at -O2 on x86_64-linux-gnu
   Product: clang
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: LLVM Codegen
  Assignee: unassignedclangb...@nondot.org
  Reporter: qrzh...@gatech.edu
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk

It appears to be a recent regression. It happens at O2 and above. O1 works
fine.

$ clang-trunk -v
clang version 11.0.0 (https://github.com/llvm/llvm-project.git
f6b2c003f360c3d0dcfe13d751805643f229f79b)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin


$ clang-trunk abc.c ; ./a.out
0

$ clang-trunk -O2 abc.c ; ./a.out
Floating point exception (core dumped)


$ cat abc.c
int printf(const char *, ...);
int a, c, d, e, f, h, i;
unsigned b, k;
short g, j;
volatile int l;
int m() {
  for (;;) {
j = 2;
for (; j >= 0; j--)
  for (; g;)
;
h = 0;
for (; h <= 2; h++)
  f &= d;
e = 0;
for (; e <= 2; e++) {
  if (k)
for (; l; l--)
  ;
  if (j) {
i = f == 0 ? 0 : b % f;
if (i)
  ;
else
  return 1;
  } else {
c = 0;
for (; c != 5; c = c + 5)
  f = 0;
  }
}
  }
}
int main() {
  m();
  printf("%X\n", a);
}

-- 
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 45361] New: fold away float to double (to float) conversion in copysign

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45361

Bug ID: 45361
   Summary: fold away float to double (to float) conversion in
copysign
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: nok.ra...@gmail.com
CC: llvm-bugs@lists.llvm.org

#include 

float foo(float x, float y)
{
return std::copysign(x, y);
}
// bug 45305-like foldable float to double promotion
float bar(float x, float y)
{
return std::copysign(x, double(y));
}
// previous + fext-ftrunc pair across copysign
float qaz(float x, float y)
{
return std::copysign(double(x), y);
}

define float @foo(float %0, float %1) {
  %3 = tail call float @llvm.copysign.f32(float %0, float %1) #2
  ret float %3
}

define float @bar(float %0, float %1) {
  %3 = fpext float %1 to double
  %4 = fpext float %0 to double
  %5 = tail call double @llvm.copysign.f64(double %4, double %3) #2
  %6 = fptrunc double %5 to float
  ret float %6
}

define float @qaz(float %0, float %1) {
  %3 = fpext float %0 to double
  %4 = fpext float %1 to double
  %5 = tail call double @llvm.copysign.f64(double %3, double %4) #2
  %6 = fptrunc double %5 to float
  ret float %6
}

https://godbolt.org/z/sKIjDg

-- 
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 41358] Bad codegen for rotate ops

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=41358

Daan Sprenkels  changed:

   What|Removed |Added

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

--- Comment #1 from Daan Sprenkels  ---
This bug was fixed in


-- 
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 45362] New: WebAssembly doesn't support LLVM bitcode-in-object format

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45362

Bug ID: 45362
   Summary: WebAssembly doesn't support LLVM bitcode-in-object
format
   Product: lld
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: wasm
  Assignee: unassignedb...@nondot.org
  Reporter: a...@crichton.co
CC: llvm-bugs@lists.llvm.org, s...@chromium.org

We've recently been working on a change [1] in rustc to how we implement LTO in
rustc itself. The change we're implementing is to leverage LLVM's support for
an object file format where the object file has native machine code but also
has LLVM bitcode embedded into a custom section. This allows us to ship
binaries which can both be natively linked but also LTO'd against without
having any auxiliary files of our own.

The WebAssembly target, however, does not support this feature. This bug is
intended to be a feature request for implementing this for the wasm target,
allowing producers to embed LLVM bitcode into a blessed section name which
would be recognized by LLVM's LTO pipeline and additionally stripped by default
in LLD. I'm currently filing this on LLD because it seems like it may mostly
affect that, but I can also move it around if that would help!

[1]: https://github.com/rust-lang/rust/pull/70458

-- 
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 45351] function static variable instantiated at -O2 despite extern template

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45351

Reid Kleckner  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||r...@google.com
 Resolution|--- |INVALID

--- Comment #1 from Reid Kleckner  ---
Clang is allowed to do this inlining. I can't site the standard, but this came
up for me personally while adding extern template decls to LLVM.

Function templates that are declared extern can be inlined if they are marked
inline. Defining a method inside a class body implicitly makes it inline. So,
to avoid the inlining without resorting to fno-inline, write the code like
this:

template 
struct S {
  int func();
};

template 
int S::func() {
  static int function_local_static = 0;
  return ++function_local_static;
}

extern template class S;

int user()
{
return S().func();
}

This will prohibit instantiation of S::func and even allow you to specialize it
out of line.

-- 
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 19815 in oss-fuzz: llvm:clang-fuzzer: ASSERT: (!needsOverloadResolutionForDestructor() || (data().DeclaredSpecialMembers & SMF

2020-03-30 Thread sheriffbot via monorail via llvm-bugs 
Updates:
Labels: Deadline-Approaching

Comment #1 on issue 19815 by sheriffbot: llvm:clang-fuzzer: ASSERT: 
(!needsOverloadResolutionForDestructor() || (data().DeclaredSpecialMembers & SMF
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19815#c1

This bug is approaching its deadline for being fixed, and will be automatically 
derestricted within 7 days. If a fix is planned within 2 weeks after the 
deadline has passed, a grace extension can be granted.

- Your friendly Sheriffbot

-- 
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 19863 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-O2: ASSERT: isa(Val) && "cast() argument of incompatible type!"

2020-03-30 Thread sheriffbot via monorail via llvm-bugs 
Updates:
Labels: Deadline-Approaching

Comment #1 on issue 19863 by sheriffbot: llvm:llvm-isel-fuzzer--aarch64-O2: 
ASSERT: isa(Val) && "cast() argument of incompatible type!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19863#c1

This bug is approaching its deadline for being fixed, and will be automatically 
derestricted within 7 days. If a fix is planned within 2 weeks after the 
deadline has passed, a grace extension can be granted.

- Your friendly Sheriffbot

-- 
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 19880 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in EvaluateObjectArgument

2020-03-30 Thread sheriffbot via monorail via llvm-bugs 
Updates:
Labels: Deadline-Approaching

Comment #1 on issue 19880 by sheriffbot: llvm:clang-fuzzer: Segv on unknown 
address in EvaluateObjectArgument
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19880#c1

This bug is approaching its deadline for being fixed, and will be automatically 
derestricted within 7 days. If a fix is planned within 2 weeks after the 
deadline has passed, a grace extension can be granted.

- Your friendly Sheriffbot

-- 
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 45342] Regression: Linker error: Required destructor

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45342

Reid Kleckner  changed:

   What|Removed |Added

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

--- Comment #4 from Reid Kleckner  ---
Looking again, yes, I think it is a duplicate. I uploaded my work in progress
patch. I think I stopped work on it because it was hard to get the access
control stuff right without modelling this as a completely new and distinct
special member.

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

-- 
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 45364] New: x86 -fcf-protection -mcmodel=large is broken

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45364

Bug ID: 45364
   Summary: x86 -fcf-protection -mcmodel=large is broken
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: X86
  Assignee: unassignedb...@nondot.org
  Reporter: efrie...@quicinc.com
CC: craig.top...@gmail.com, hjl.to...@gmail.com,
llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk,
spatel+l...@rotateright.com, xiang1.zh...@intel.com

Testcase:

void ext();
__attribute((noinline)) static void a() { ext(); }
void b() { a(); }

Compile with "clang -O2 -mcmodel=large -fcf-protection".  Note the indirect
call to "a", which does not have an endbr.

-- 
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 45279] Assertion failed: (CAT && "unexpected type for array initializer"), function VisitCXXNewExpr, file clang/lib/AST/ExprConstant.cpp, line 8690.

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45279

Richard Smith  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Richard Smith  ---
Duplicate of PR45350; compilation succeeds with Clang trunk.

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

-- 
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 21521 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclSpec::Finish

2020-03-30 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 Stability-Memory-AddressSanitizer Reproducible 
Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-03-30
Type: Bug

New issue 21521 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in 
clang::DeclSpec::Finish
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21521

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

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

Crash Type: Stack-overflow
Crash Address: 0x7ffe2974ee60
Crash State:
  clang::DeclSpec::Finish
  clang::Parser::ParseTypeQualifierListOpt
  clang::Parser::ParseDeclaratorInternal
  
Sanitizer: address (ASAN)

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

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

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 45365] New: ppc64le: including prior to causes compilation to fail in C mode

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45365

Bug ID: 45365
   Summary: ppc64le: including  prior to 
causes compilation to fail in C mode
   Product: clang
   Version: 10.0
  Hardware: Other
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: cl...@evan.coeusgroup.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

This is trivial to reproduce:

  #include 
  #include 

And compile with clang (not clang++).  The result is lots of "error: unknown
type name 'vector'".

AFAICT the problem is that stdbool.h defines bool to _Bool, then gets confused
when using types like "vector bool char" (which is "vector _Bool char" after
preprocessing).

I'm not really sure why, but it works in GCC.  Maybe they just treat _Bool the
same as bool for AltiVec.  It would be really nice if clang worked, 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 43360] [meta] 9.0.1 Release Blockers

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=43360
Bug 43360 depends on bug 41027, which changed state.

Bug 41027 Summary: Inline asm validation doesn't use delayed warnings
https://bugs.llvm.org/show_bug.cgi?id=41027

   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 41027] Inline asm validation doesn't use delayed warnings

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=41027

Jörg Sonnenberger  changed:

   What|Removed |Added

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

--- Comment #28 from Jörg Sonnenberger  ---
Since the fix is in 10.0, drop the merge. Third parties can merge the remaining
part of the fix if they really need 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 37219] Warn when movq is used with a 64bit immediate

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=37219

Jörg Sonnenberger  changed:

   What|Removed |Added

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

--- Comment #2 from Jörg Sonnenberger  ---
Implemented at some point in 2018

-- 
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 14218] Redeclaration of "log" shows incorrect note

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=14218

Jörg Sonnenberger  changed:

   What|Removed |Added

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

--- Comment #4 from Jörg Sonnenberger  ---
Has been fixed at least since 7.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 20969] [mips] Unsupported s.d macro

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=20969

Jörg Sonnenberger  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Jörg Sonnenberger  ---
This seems to work now.

-- 
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 21522 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator

2020-03-30 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 Stability-Memory-AddressSanitizer Reproducible 
Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-03-31
Type: Bug

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

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

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

Crash Type: Stack-overflow
Crash Address: 0x7fff96c7cd88
Crash State:
  GetFullTypeForDeclarator
  clang::Sema::GetTypeForDeclarator
  clang::Sema::ActOnBlockArguments
  
Sanitizer: address (ASAN)

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

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

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 45259] When compiling with -O2: Assertion `getTypeSizeInBits(SrcTy) <= getTypeSizeInBits(Ty) && "getNoopOrZeroExtend cannot truncate!"' failed.

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45259

Vedant Kumar  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Fixed By Commit(s)||dcc410b5cf202e354105df431fa
   ||d62d2f5f7eac7
 Status|CONFIRMED   |RESOLVED

-- 
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 42315] llgo build failure

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=42315

Nathan Chancellor  changed:

   What|Removed |Added

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

--- Comment #3 from Nathan Chancellor  ---
This is resolved by the nature of llgo being removed from the tree.

-- 
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 45366] New: [PPC] Assertion failed:`isVariable() && "Invalid accessor!"'

2020-03-30 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45366

Bug ID: 45366
   Summary: [PPC] Assertion failed:`isVariable() && "Invalid
accessor!"'
   Product: tools
   Version: 10.0
  Hardware: Other
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: llc
  Assignee: unassignedb...@nondot.org
  Reporter: v.chur...@gmail.com
CC: llvm-bugs@lists.llvm.org

We are observing segmentation faults and corresponding assertion errors on PPC
since upgrading to LLVM 8/9/10 from LLVM 6.

Corresponding downstream issue: https://github.com/JuliaLang/julia/issues/35025

The assertion error for LLVM 9 is:

```
julia-debug:
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/include/llvm/MC/MCSymbol.h:303:
const llvm::MCExpr* llvm::MCSymbol::getVariableValue(bool) const: Assertion
`isVariable() && "Invalid accessor!"' failed.

signal (6): Aborted
in expression starting at none:0
gsignal at /lib64/libc.so.6 (unknown line)
abort at /lib64/libc.so.6 (unknown line)
__assert_fail_base at /lib64/libc.so.6 (unknown line)
__assert_fail at /lib64/libc.so.6 (unknown line)
getVariableValue at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/include/llvm/MC/MCSymbol.h:303
finish at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp:199
Finish at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/MC/MCStreamer.cpp:911
doFinalization at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:1666
doFinalization at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/Target/PowerPC/PPCAsmPrinter.cpp:1386
doFinalization at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/IR/LegacyPassManager.cpp:1703
runOnModule at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/IR/LegacyPassManager.cpp:1779
run at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/IR/LegacyPassManager.cpp:1863
run at
/home/vchuravy/julia/deps/srccache/llvm-9.0.1/lib/IR/LegacyPassManager.cpp:1894
operator() at /home/vchuravy/julia/src/jitlayers.cpp:1025
jl_dump_native at /home/vchuravy/julia/src/jitlayers.cpp:1064
jl_write_compiler_output at /home/vchuravy/julia/src/precompile.c:93
jl_atexit_hook at /home/vchuravy/julia/src/init.c:227
main at /home/vchuravy/julia/ui/repl.c:218
generic_start_main.isra.0 at /lib64/libc.so.6 (unknown line)
__libc_start_main at /lib64/libc.so.6 (unknown line)
Allocations: 160184348 (Pool: 160149044; Big: 35304); GC: 158
```

I was unsuccessful in reproducing it outside Julia sofar.

A corresponding segmentation fault in LLVM10 looks like:

```
signal (11): Segmentation fault
in expression starting at none:0
_ZN12_GLOBAL__N_120PPCTargetELFStreamer6finishEv at
/buildworker/worker/package_linuxppc64le/build/usr/bin/../lib/libLLVM-10jl.so
(unknown line)
Allocations: 159123504 (Pool: 159085215; Big: 38289); GC: 131
Segmentation fault (core dumped)
make[1]: ***
[/buildworker/worker/package_linuxppc64le/build/usr/lib/julia/sys-o.a] Error 1
```

To reproduce with Julia:

```
git clone https://github.com/JuliaLang/julia
git checkout vc/upgrade_llvm_10

cat <> Make.user
USE_BINARYBUILDER=0
LLVM_DEBUG=1
LLVM_ASSERTIONS=1
FORCE_ASSERTIONS=1
EOT
```

I will continue to try to reproduce this outside Julia

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