[llvm-bugs] [Bug 33961] New: opt crashes with "opt -sroa -jump-threading -loop-deletion"

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33961

Bug ID: 33961
   Summary: opt crashes with "opt -sroa -jump-threading
-loop-deletion"
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: s...@cs.ucdavis.edu
CC: llvm-bugs@lists.llvm.org

$ clang -v
clang version 6.0.0 (trunk 309139)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/clang-trunk/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.4
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.2.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
$
$ clang -O3 -mllvm -disable-llvm-optzns -c -emit-llvm -o small.bc small.c
$ opt -sroa -jump-threading -loop-deletion -o small-opt.bc small.bc
While deleting: i32 %
Use still stuck around after Def is destroyed:  %f.0 = phi i32 [ 0, %entry ], [
, %while.end9 ]
opt: /tmp/llvm-builder/llvm-source-trunk/lib/IR/Value.cpp:86:
llvm::Value::~Value(): Assertion `use_empty() && "Uses remain when a value is
destroyed!"' failed.
#0 0x01f428ea (opt+0x1f428ea)
#1 0x01f40a7e (opt+0x1f40a7e)
#2 0x01f40be0 (opt+0x1f40be0)
#3 0x7f8c37be7330 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x10330)
#4 0x7f8c369cfc37 gsignal
/build/eglibc-SvCtMH/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0
#5 0x7f8c369d3028 abort
/build/eglibc-SvCtMH/eglibc-2.19/stdlib/abort.c:91:0
#6 0x7f8c369c8bf6 __assert_fail_base
/build/eglibc-SvCtMH/eglibc-2.19/assert/assert.c:92:0
#7 0x7f8c369c8ca2 (/lib/x86_64-linux-gnu/libc.so.6+0x2fca2)
#8 0x01aae2db (opt+0x1aae2db)
#9 0x01aae3f0 (opt+0x1aae3f0)
#10 0x019b6216 (opt+0x19b6216)
#11 0x019b7705 (opt+0x19b7705)
#12 0x01d906b8 (opt+0x1d906b8)
#13 0x01d92739 (opt+0x1d92739)
#14 0x0155b95b (opt+0x155b95b)
#15 0x01a6b863 (opt+0x1a6b863)
#16 0x01a6b90c (opt+0x1a6b90c)
#17 0x01a6c5aa (opt+0x1a6c5aa)
#18 0x007e936b (opt+0x7e936b)
#19 0x7f8c369baf45 __libc_start_main
/build/eglibc-SvCtMH/eglibc-2.19/csu/libc-start.c:321:0
#20 0x0084878a (opt+0x84878a)
Stack dump:
0.  Program arguments: opt -sroa -jump-threading -loop-deletion -o
small-opt.bc small.bc
1.  Running pass 'Function Pass Manager' on module 'small.bc'.
2.  Running pass 'Loop Pass Manager' on function '@fn1'
3.  Running pass 'Delete dead loops' on value 'Segmentation fault (core
dumped)
$


-


int a, b, c, d;

void fn1 ()
{ 
  int f = 0;
L:
  if (f)
for (d = 0; d;)
  if (((f = c) || 1) & 0)
{ 
  while (b)
while (a)
  ;
  goto L;
}
}

int main ()
{ 
  fn1 ();
  return 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 33962] New: clang-format unexpected token with "}" a comment block

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33962

Bug ID: 33962
   Summary: clang-format unexpected token with "}" a comment block
   Product: clang
   Version: 5.0
  Hardware: PC
OS: Windows XP
Status: NEW
  Severity: normal
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: patrick.st...@tomra.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org

Created attachment 18858
  --> https://bugs.llvm.org/attachment.cgi?id=18858&action=edit
Used .clang-format configuration file

The following code causes an error in clang-format:

void f()
{
if (true)
{
/*Hello*/}
}

The error message is: '5' is unexpected token. The expected token is '"' or ''.
Line2, position 66.

By moving the closing } to the next line, the error is gone:

void f()
{
if (true)
{
/*Hello*/
}
}

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


[llvm-bugs] [Bug 32112] Missing relocations with ld.lld-4.0 and -target=x86_64 and -fpie

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=32112

George Rimar  changed:

   What|Removed |Added

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

--- Comment #3 from George Rimar  ---
r309252

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


[llvm-bugs] [Bug 33963] New: opt crashes with "opt -sroa -adce -lcssa -indvars": Assertion `L->isRecursivelyLCSSAForm(*DT, *LI) && "Requested to preserve LCSSA, but it's already broken."' failed

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33963

Bug ID: 33963
   Summary: opt crashes with "opt -sroa -adce -lcssa -indvars":
Assertion `L->isRecursivelyLCSSAForm(*DT, *LI) &&
"Requested to preserve LCSSA, but it's already
broken."' failed
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: s...@cs.ucdavis.edu
CC: llvm-bugs@lists.llvm.org

$ clang -v
clang version 6.0.0 (trunk 309139)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/clang-trunk/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
$
$ clang -O3 -mllvm -disable-llvm-optzns -w -c -emit-llvm -o small.bc small.c
$ opt -sroa -adce -lcssa -indvars -o small-opt.bc small.bc
opt:
/tmp/llvm-builder/llvm-source-trunk/lib/Transforms/Utils/LoopSimplify.cpp:697:
bool llvm::simplifyLoop(llvm::Loop*, llvm::DominatorTree*, llvm::LoopInfo*,
llvm::ScalarEvolution*, llvm::AssumptionCache*, bool): Assertion
`L->isRecursivelyLCSSAForm(*DT, *LI) && "Requested to preserve LCSSA, but it's
already broken."' failed.
#0 0x01e69d9a (opt+0x1e69d9a)
#1 0x01e67b0e (opt+0x1e67b0e)
#2 0x01e67c82 (opt+0x1e67c82)
#3 0x7ffa6390b390 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x7ffa6267d428 gsignal
/build/glibc-bfm8X4/glibc-2.23/signal/../sysdeps/unix/sysv/linux/raise.c:54:0
#5 0x7ffa6267f02a abort /build/glibc-bfm8X4/glibc-2.23/stdlib/abort.c:91:0
#6 0x7ffa62675bd7 __assert_fail_base
/build/glibc-bfm8X4/glibc-2.23/assert/assert.c:92:0
#7 0x7ffa62675c82 (/lib/x86_64-linux-gnu/libc.so.6+0x2dc82)
#8 0x01eeb3b1 (opt+0x1eeb3b1)
#9 0x01eeb62f (opt+0x1eeb62f)
#10 0x0195aa23 (opt+0x195aa23)
#11 0x0195aaec (opt+0x195aaec)
#12 0x0195a58d (opt+0x195a58d)
#13 0x006dd75c (opt+0x6dd75c)
#14 0x7ffa62668830 __libc_start_main
/build/glibc-bfm8X4/glibc-2.23/csu/../csu/libc-start.c:325:0
#15 0x00749e49 (opt+0x749e49)
Stack dump:
0.  Program arguments: opt -sroa -adce -lcssa -indvars -o small-opt.bc
small.bc
1.  Running pass 'Function Pass Manager' on module 'small.bc'.
2.  Running pass 'Canonicalize natural loops' on function '@f'
Aborted (core dumped)
$


--


int a, c, d;

void e (int b) {}

void f ()
{ 
  int g = 4;
  while (0)
g = 0;
  while (0)
{ 
  int h;
  c && 6;
  if (h)
continue;
}
  while (0)
a || 0;
  for (; 0; d)
{ 
  e (g);
  while (1)
{ 
  int i;
  if (f)
continue;
}
}
}

int main ()
{ 
  f ();
  return 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 32112] Missing relocations with ld.lld-4.0 and -target=x86_64 and -fpie

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=32112

George Rimar  changed:

   What|Removed |Added

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

--- Comment #4 from George Rimar  ---
Fix was reverted in r309258.

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


[llvm-bugs] [Bug 32056] Invalid code generation (aliasing between scalar and vector type)

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=32056

Wenzel Jakob  changed:

   What|Removed |Added

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

--- Comment #15 from Wenzel Jakob  ---
I'll close the issue as D33328 was merged, which indeed fixes the testcase that
prompted this issue.

Thanks,
Wenzel

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


[llvm-bugs] [Bug 33964] New: Returning copy of heap allocated class in switch statement leads to crash

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33964

Bug ID: 33964
   Summary: Returning copy of heap allocated class in switch
statement leads to crash
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: LLVM Codegen
  Assignee: unassignedclangb...@nondot.org
  Reporter: dr...@chromium.org
CC: llvm-bugs@lists.llvm.org

Created attachment 18860
  --> https://bugs.llvm.org/attachment.cgi?id=18860&action=edit
FontStyleResolver-8a192c.cpp

Compiling the attached reduction using:
$ clang -cc1 -emit-obj -Oz -std=gnu++11  -x c++ FontStyleResolver-8a192c.cpp

$ clang  --version
clang version 5.0.0 (trunk 307486)

leads to the following stack trace, see below.

When turning NormalSlopeValue() and ItalicSlopeValue() into functions that
return static const FontSelectionValueStyle& instead of static const
FontSelectionValueStyle, the issue does not occur.


clang:
/b/build/slave/linux_upload_clang/build/src/third_party/llvm/lib/CodeGen/MachineBasicBlock.cpp:56:
llvm::MCSymbol *llvm::MachineBasicBlock::getSymbol() const: Assertion
`getNumber() >= 0 && "cannot get label for unreachable MBB"' failed.
#0 0x01d59574
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x1d59574)
#1 0x01d59896
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x1d59896)
#2 0x7facf7efe330 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x10330)
#3 0x7facf6aeec37 gsignal
/build/eglibc-SvCtMH/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0
#4 0x7facf6af2028 abort
/build/eglibc-SvCtMH/eglibc-2.19/stdlib/abort.c:91:0
#5 0x7facf6ae7bf6 __assert_fail_base
/build/eglibc-SvCtMH/eglibc-2.19/assert/assert.c:92:0
#6 0x7facf6ae7ca2 (/lib/x86_64-linux-gnu/libc.so.6+0x2fca2)
#7 0x015c8b25
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x15c8b25)
#8 0x01196892
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x1196892)
#9 0x01197e7c
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x1197e7c)
#10 0x01194373
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x1194373)
#11 0x0237b788 llvm::AsmPrinter::EmitFunctionBody()
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x237b788)
#12 0x0118de70
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x118de70)
#13 0x015fc0c4
llvm::MachineFunctionPass::runOnFunction(llvm::Function&)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x15fc0c4)
#14 0x018d9ddf llvm::FPPassManager::runOnFunction(llvm::Function&)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x18d9ddf)
#15 0x018da033 llvm::FPPassManager::runOnModule(llvm::Module&)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x18da033)
#16 0x018da526 llvm::legacy::PassManagerImpl::run(llvm::Module&)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x18da526)
#17 0x01ed417f clang::EmitBackendOutput(clang::DiagnosticsEngine&,
clang::HeaderSearchOptions const&, clang::CodeGenOptions const&,
clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout
const&, llvm::Module*, clang::BackendAction,
std::unique_ptr >)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x1ed417f)
#18 0x026057c2
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x26057c2)
#19 0x02a6ff56 clang::ParseAST(clang::Sema&, bool, bool)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x2a6ff56)
#20 0x022c3778 clang::FrontendAction::Execute()
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x22c3778)
#21 0x02273f01
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x2273f01)
#22 0x0234bb7a
clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x234bb7a)
#23 0x008437d4 cc1_main(llvm::ArrayRef, char const*,
void*)
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+Asserts/bin/clang+0x8437d4)
#24 0x0084138e main
(/usr/local/google/home/drott/dev/blink/src/third_party/llvm-build/Release+

[llvm-bugs] [Bug 33937] utils/lit/tests/selecting.py fails on Windows

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33937

Brian Gesiak  changed:

   What|Removed |Added

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

--- Comment #2 from Brian Gesiak  ---
Ah, sorry, I think I may have marked this as XFAIL on Windows by mistake. The
test was failing on all environments at the time, before
https://reviews.llvm.org/D35867 was merged. Sorry for the inconvenience!

I'm curious: did you notice the failure because you run the lit test suite on
Windows frequently? The lit test suite has been failing for around a month or
so; were your runs also failing?

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


[llvm-bugs] [Bug 33936] utils/lit/tests/shtest-encoding.py fails on Windows

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33936

Brian Gesiak  changed:

   What|Removed |Added

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

--- Comment #2 from Brian Gesiak  ---
That's strange, it was definitely failing for me before... I apologize for
having marked this XFAIL, and for not attaching logs as part of the original
report. I was hoping to create the bugs, then circle back and add details on
how they fail for each -- https://bugs.llvm.org/show_bug.cgi?id=33939, for
example, does still fail for me, and I commented with some logs to demonstrate.

In any case, sorry again for the inconvenience!

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


[llvm-bugs] [Bug 33792] Move IndirectCallPromotion to new OptRemark API

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33792

Adam Nemet  changed:

   What|Removed |Added

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

--- Comment #2 from Adam Nemet  ---
Landed in r309294

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


[llvm-bugs] [Bug 33789] Remove old OptRemark API

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33789
Bug 33789 depends on bug 33792, which changed state.

Bug 33792 Summary: Move IndirectCallPromotion to new OptRemark API
https://bugs.llvm.org/show_bug.cgi?id=33792

   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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 33682] endianness bug in visitTRUNCATE

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33682

Simon Pilgrim  changed:

   What|Removed |Added

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

--- Comment #11 from Simon Pilgrim  ---
Fixed in trunk rL308960

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


[llvm-bugs] [Bug 33965] New: compute_schedule: Invaliad write

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33965

Bug ID: 33965
   Summary: compute_schedule: Invaliad write
   Product: Polly
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: isl
  Assignee: polly-...@googlegroups.com
  Reporter: l...@meinersbur.de
CC: llvm-bugs@lists.llvm.org

Created attachment 18866
  --> https://bugs.llvm.org/attachment.cgi?id=18866&action=edit
symm_0.ll

The attached test case segfault while isl computes a schedule.

$ bin/opt  -polly-process-unprofitable-polly-opt-isl -S < symm_0.ll
Segmentation fault (core dumped)

Valgrind memcheck report:
$ valgrind bin/opt  -polly-process-unprofitable -polly-opt-isl -S < symm_0.ll
==22670== Memcheck, a memory error detector
==22670== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==22670== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==22670== Command: bin/opt -polly-process-unprofitable -polly-remarks-minimal
-polly-use-llvm-names
-polly-import-jscop-dir=/mnt/c/Users/Meinersbur/src/llvm/tools/polly/test
-polly-opt-isl -S
==22670==
==22670== Invalid write of size 4
==22670==at 0x1CFF90C: isl_dim_map_range (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C91BF0: inter_dim_map.isra.31 (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C95E91: lp_add_inter (in /root/build/llvm/release/bin/opt)
==22670==by 0x1CA1FE0: isl_basic_set_list_foreach (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C907C3: setup_carry_lp (in /root/build/llvm/release/bin/opt)
==22670==by 0x1C97E5C: carry (in /root/build/llvm/release/bin/opt)
==22670==by 0x1C9871A: compute_schedule_finish_band (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C99CE1: compute_schedule_wcc (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C9C577: compute_component_schedule.constprop.58 (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C9C8CD: isl_schedule_constraints_compute_schedule (in
/root/build/llvm/release/bin/opt)
==22670==by 0x168B05B: (anonymous
namespace)::IslScheduleOptimizer::runOnScop(polly::Scop&) [clone .part.105]
[clone .constprop.156] (in /root/build/llvm/release/bin/opt)
==22670==by 0x168C2D0: (anonymous
namespace)::IslScheduleOptimizer::runOnScop(polly::Scop&) (in
/root/build/llvm/release/bin/opt)
==22670==  Address 0x6d267cc is 4 bytes before an unallocated block of size
79,888 in arena "client"
==22670==
==22670== Invalid write of size 4
==22670==at 0x1CFF916: isl_dim_map_range (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C91BF0: inter_dim_map.isra.31 (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C95E91: lp_add_inter (in /root/build/llvm/release/bin/opt)
==22670==by 0x1CA1FE0: isl_basic_set_list_foreach (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C907C3: setup_carry_lp (in /root/build/llvm/release/bin/opt)
==22670==by 0x1C97E5C: carry (in /root/build/llvm/release/bin/opt)
==22670==by 0x1C9871A: compute_schedule_finish_band (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C99CE1: compute_schedule_wcc (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C9C577: compute_component_schedule.constprop.58 (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C9C8CD: isl_schedule_constraints_compute_schedule (in
/root/build/llvm/release/bin/opt)
==22670==by 0x168B05B: (anonymous
namespace)::IslScheduleOptimizer::runOnScop(polly::Scop&) [clone .part.105]
[clone .constprop.156] (in /root/build/llvm/release/bin/opt)
==22670==by 0x168C2D0: (anonymous
namespace)::IslScheduleOptimizer::runOnScop(polly::Scop&) (in
/root/build/llvm/release/bin/opt)
==22670==  Address 0x6d267d0 is 0 bytes inside an unallocated block of size
79,888 in arena "client"
==22670==
==22670== Invalid write of size 4
==22670==at 0x1CFF90C: isl_dim_map_range (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C91C48: inter_dim_map.isra.31 (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C95E91: lp_add_inter (in /root/build/llvm/release/bin/opt)
==22670==by 0x1CA1FE0: isl_basic_set_list_foreach (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C907C3: setup_carry_lp (in /root/build/llvm/release/bin/opt)
==22670==by 0x1C97E5C: carry (in /root/build/llvm/release/bin/opt)
==22670==by 0x1C9871A: compute_schedule_finish_band (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C99CE1: compute_schedule_wcc (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C9C577: compute_component_schedule.constprop.58 (in
/root/build/llvm/release/bin/opt)
==22670==by 0x1C9C8CD: isl_schedule_constraints_compute_schedule (in
/root/build/llvm/release/bin/opt)
==22670==by 0x168B05B: (anonymous
namespace)::IslScheduleOptimizer::runOnScop(polly::Scop&) [clone .part.105]
[clone .constprop.156] (in /root/build/llvm/release/b

[llvm-bugs] [Bug 33966] New: cfi-icall + ThinLTO: does not include function decl/def names in hash used for caching

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33966

Bug ID: 33966
   Summary: cfi-icall + ThinLTO: does not include function
decl/def names in hash used for caching
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Interprocedural Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: pe...@pcc.me.uk
CC: llvm-bugs@lists.llvm.org

$ cat 1.c
void f(void);

void* _start(void (*p)(void)) {
  p();
  return f;
}
$ cat 2.c
void f(void) {}
$ rm -rf cache/
$ clang -c -flto=thin -fsanitize=cfi-icall 1.c -O
$ clang -c  2.c -O
$ ld.lld 1.o 2.o --thinlto-cache-dir=cache
$ clang -c -flto=thin -fsanitize=cfi-icall 2.c -O
$ ld.lld 1.o 2.o --thinlto-cache-dir=cache
ld.lld: error: undefined symbol: f.cfi_jt
>>> referenced by 1.c
>>>   
>>> cache/llvmcache-88B852A71DDDCDEA532AB952595D5ACDDE9A1936:(_start)

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


[llvm-bugs] [Bug 33967] New: TBAA leads to incorrect code generation (aliasing between scalar and SSE vector type)

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33967

Bug ID: 33967
   Summary: TBAA leads to incorrect code generation (aliasing
between scalar and SSE vector type)
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: LLVM Codegen
  Assignee: unassignedclangb...@nondot.org
  Reporter: wenzel.ja...@epfl.ch
CC: llvm-bugs@lists.llvm.org

Consider the simple snippet of C++ code below, which performs type punning
between an SSE vector register type (__m128) and the underlying scalar type.

Although it may look contrived here, these types of constructions are essential
to implement efficient vector math libraries that use intrinsics internally
while providing standard C accessors to interface with the outside world.
When compiled on my machine (with "clang++ test.cpp -std=c++11 -O3 -msse4.2 -o
test"), I observe the following output 

0.00 1.00 2.00 3.00 4.00 0.00 6.00 7.00
 (^ note the zero value here, which
should be 5)

If compiled with -fno-strict-aliasing, the fifth entry is equal to 5.00,
confirming that this is indeed an aliasing optimization-related issue.

In several of my projects developing, this leads to incorrect/inconsistent
results, and the only workaround is to disable aliasing -- obviously not a good
long-term solution as this is highly optimized / performance-sensitive code.
As vector instructions (AVX512, new ARM vector instructions, etc.) are becoming
an increasingly essential ingredient of efficient code, it would be great to
finally address this issue.

A related issue was discussed in Bug 32056, which focused on a case where the
relationship is made more explicit using a 'union' type annotation. The issue
here targets an orthogonal problem -- what the aliasing relationship of a
vector
type and its underlying scalar type should be.

At a technical level, it appears that this is not that hard to resolve -- Hal
Finkel (https://reviews.llvm.org/D31885) wrote: "[this issue] if desired,
should just be fixed (the vector type should be a child of the scalar element
type in the current representation).""

Thank you,
Wenzel

=== C++ snippet =

#include 
#include 

struct A {
A () {
a = _mm_setr_ps(0.f, 1.f, 2.f, 3.f);
b = _mm_setr_ps(4.f, 5.f, 6.f, 7.f);
}

const float *begin() { return (float *) &a; }
const float *end() { return (float *) &a + 8; }

__m128 a, b;
};

int main(int argc, char *argv[]) {
A a;
for (float value : a)
printf("%f ", value);

return 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 26928] Prune the include path for modules

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=26928

Bruno Cardoso Lopes  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #4 from Bruno Cardoso Lopes  ---
This is no longer a issue, it got fixed after several commits to clang and
libcxx in the past year, mostly due to the introduction of
no_undeclared_includes, which allowed fixing the root cause of the cycle issue
in r284797.

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


[llvm-bugs] [Bug 27449] Retire the non-deterministic ASTFileSignature

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=27449

Bruno Cardoso Lopes  changed:

   What|Removed |Added

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

--- Comment #4 from Bruno Cardoso Lopes  ---
This was fixed in r297655 -> Modules: Use hash of PCM content for SIGNATURE

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


[llvm-bugs] [Bug 33968] New: clang_getCompletionParent does not allow retrieving template arguments

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33968

Bug ID: 33968
   Summary: clang_getCompletionParent does not allow retrieving
template arguments
   Product: clang
   Version: 4.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: libclang
  Assignee: unassignedclangb...@nondot.org
  Reporter: m...@svenbrauch.de
CC: kli...@google.com, llvm-bugs@lists.llvm.org

In code like the following:

template
struct X {
void f();
};
int main() {
x = X();
x.|
}

when retrieving completion items at the place marked with |, the completion
parent as given by clang_getCompletionParent is "X". It would however be useful
(or rather, necessary in some situations) to know that it is X. I'm not
sure how this should be represented API-wise; if you suggest something, I can
try to come up with a patch. Maybe just returning "X" from
clang_getCompletionParent would be acceptable?

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


[llvm-bugs] [Bug 33957] clang 5.0 segfaults compiling ghostscript

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33957

Davide Italiano  changed:

   What|Removed |Added

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

--- Comment #5 from Davide Italiano  ---
r309330

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


[llvm-bugs] [Bug 33849] [meta] 5.0.0 Release Blockers

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33849
Bug 33849 depends on bug 33957, which changed state.

Bug 33957 Summary: clang 5.0 segfaults compiling ghostscript
https://bugs.llvm.org/show_bug.cgi?id=33957

   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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 33960] crash at -O3 in both 32-bit and 64-bit modes on x86_64-linux-gnu (Assertion `(InMaskOpc == ISD::SETCC || ISD::isBuildVectorOfConstantSDNodes(InMask.getNode()) || (isLogicalMask

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33960

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #4 from Hans Wennborg  ---
(In reply to Simon Pilgrim from comment #3)
> (In reply to Simon Pilgrim from comment #2)
> > Fixed in trunk rL309302
> 
> Hans - should rL309302 be merged into 5.000? Its purely an assertion fix but
> has been coming up quite a bit recently.

Sounds good. Merged in r309348, and marking as 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 33849] [meta] 5.0.0 Release Blockers

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33849
Bug 33849 depends on bug 33960, which changed state.

Bug 33960 Summary: crash at -O3 in both 32-bit and 64-bit modes on 
x86_64-linux-gnu (Assertion `(InMaskOpc == ISD::SETCC || 
ISD::isBuildVectorOfConstantSDNodes(InMask.getNode()) || 
(isLogicalMaskOp(InMaskOpc) && isSETCCorConvertedSETCC(InMask->getOperand(0)) 
&& isSETCCorCon
https://bugs.llvm.org/show_bug.cgi?id=33960

   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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 33849] [meta] 5.0.0 Release Blockers

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33849
Bug 33849 depends on bug 33917, which changed state.

Bug 33917 Summary: Miscompilation with `-jump-threading 
-correlated-propagation` and llvm.assume
https://bugs.llvm.org/show_bug.cgi?id=33917

   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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 33917] Miscompilation with `-jump-threading -correlated-propagation` and llvm.assume

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33917

Davide Italiano  changed:

   What|Removed |Added

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

--- Comment #17 from Davide Italiano  ---
r309353/r309355.

Hans, we might consider backporting this to 5.0 as it's blocking the Rust
people.

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


[llvm-bugs] [Bug 33953] .cfi_return_column not supported

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33953

Saleem Abdulrasool  changed:

   What|Removed |Added

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

--- Comment #2 from Saleem Abdulrasool  ---
SVN r309360

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


[llvm-bugs] [Bug 33969] New: CreateLoopUnrollPass does not honor the provided loop count

2017-07-27 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33969

Bug ID: 33969
   Summary: CreateLoopUnrollPass does not honor the provided loop
count
   Product: libraries
   Version: 4.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Transformation Utilities
  Assignee: unassignedb...@nondot.org
  Reporter: agu...@tifr.res.in
CC: llvm-bugs@lists.llvm.org

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