[llvm-bugs] [Bug 28766] New: Xbox Tech 1 855 338 0710 Xbox Customer Support Number

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28766

Bug ID: 28766
   Summary: Xbox Tech 1 855 338 0710 Xbox Customer Support Number
   Product: OpenMP
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Clang Compiler Support
  Assignee: unassignedclangb...@nondot.org
  Reporter: samitasinh...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

xbox one tech support phone number   
xbox live support phone   
xbox live account support number   
xbox support phone   
xbox service phone number   
xbox live account phone number   
xbox com support number   
xbox 360 tech support phone number   
call xbox customer support   
xbox one customer service phone number   
xbox live billing phone number   
xbox live troubleshooting   
customer service xbox   
1800 for my xbox   
xbox live support telephone number   
xbox live problems   
call xbox live support   
xbox live 800 number   
xbox number call   
xbox one tech support number   
support xbox live   
xbox one customer support phone number   
xbox one helpline number   
xbox one help number   
xbox contact support   
xbox billing phone number   
contact xbox phone number   
xbox customer service telephone number   
xbox 1 customer support   
xbox one 1800 number   
xbox phone number customer service
1800 my xbox
xbox 1 phone number
xbox live account support
contact xbox live customer service
xbox support call
xbox live service

-- 
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 28767] New: Clang miscompiles placement-new

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28767

Bug ID: 28767
   Summary: Clang miscompiles placement-new
   Product: clang
   Version: trunk
  Hardware: All
OS: All
Status: NEW
  Keywords: miscompilation
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: hst...@ca.ibm.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

In the following program, the only iteration of the loop increments the int
object pointed-to by p, and then replaces said object via q using
placement-new.

Clang miscompiles at -O1 at least on x86_64-unknown-linux-gnu and
powerpc64le-unknown-linux-gnu.

Observation: passes with -fno-strict-aliasing.

Observation: -mllvm -print-before-all is indistinguishable between the
placement-new and the commented-out reinterpret_cast.

Online compiler: http://melpon.org/wandbox/permlink/h0aEUwT90gAnbGtv

### SOURCE ():
void *operator new(decltype(sizeof 0), void *) noexcept;
extern "C" void abort();

typedef int A;
typedef float B;

B *qq;

void foo(A *p, A *q, long unk) {
   for (long i = 0; i < unk; ++i) {
  ++*p;
  qq = new (static_cast(&q[i])) B(42);
  // Note: the following is a TBAA violation.
  //qq = &(*reinterpret_cast(static_cast(&q[i])) = B(42));
   }
}

void (*volatile fp)(A *, A *, long);

int main(void) {
   union { A x; B f; } u = { 0 };
   fp = foo;
   fp(&u.x, &u.x, 1);
   if (*qq != 42) abort();
}


### COMMANDS TO REPRODUCE:
clang -O1 -o ./a.out -x c++ -std=c++11 -
./a.out


### EXPECTED OUTPUT:
(rc=0)


### ACTUAL OUTPUT:
Aborted (core dumped)
Return:  0x86:134


### COMPILER VERSION INFO (clang -v):
clang version 4.0.0 (trunk 276983) (llvm/trunk 276982)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/llvm-head/bin
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.3
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64

-- 
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 28766] Xbox Tech 1 855 338 0710 Xbox Customer Support Number

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28766

Diana Picus  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 CC||diana.pi...@linaro.org
 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 26947] i386 Linux core files are not supported

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26947

dvlahov...@google.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||dvlahov...@google.com
 Resolution|--- |FIXED

--- Comment #2 from dvlahov...@google.com ---
Fixed in commit: 4d630a1a00de3c619fe7511209251a224df89790

-- 
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 28756] Xbox Tech 1 855 338 0710 Xbox Customer Support Number

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28756

Jason Dave  changed:

   What|Removed |Added

 Resolution|INVALID |MOVED

--- Comment #2 from Jason Dave  ---
**① ⑧⑤⑤ ③③⑧ ⓪⑦①⓪ ♋ Xbox Live Support Number
1-855-338-0710 Xbox Live Support Number**

[Xbox Live Support Number 1 855 338 0710][1]

We're happy to help you 24/7 call us 1 855 338 0710

Xbox Live Support Number 1 855 338 0710
  [1]: http://xboxlivesupportnume.site123.me/

-- 
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 28768] New: No way to obtain the opcode of a BinaryExpr from the C API

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28768

Bug ID: 28768
   Summary: No way to obtain the opcode of a BinaryExpr from the C
API
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: libclang
  Assignee: unassignedclangb...@nondot.org
  Reporter: eternal...@gmail.com
CC: kli...@google.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

This results in anyone unable to use the C++ API (specifically, bindings) being
unable to use libclang for actually parsing C, driving them to use other tools
(such as the Haskell Language.C library).

Relevant:

Corrode didn't use libclang due to it missing this (among other things):
https://github.com/jameysharp/corrode/issues/50#issuecomment-236098060

The libclang Rust bindings would support it if available:
https://github.com/KyleMayes/clang-rs/issues/5

-- 
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 28769] New: Coverage data includes call to __cxx_global_array_dtor

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28769

Bug ID: 28769
   Summary: Coverage data includes call to __cxx_global_array_dtor
   Product: clang
   Version: 3.9
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: llvm.flamef...@spamgourmet.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

Created attachment 16834
  --> https://llvm.org/bugs/attachment.cgi?id=16834&action=edit
GCOV file

I was using clang++ with the --coverage flag to generate coverage data on a
larger project (https://github.com/Return-To-The-Roots/s25client)
However I see an completely unexpected call to "__cxx_global_array_dtor" in the
gcno file which should not be there and leads to false positives. The line I've
seen this is this one:
https://github.com/Return-To-The-Roots/s25client/blob/14796d1cb7423a87f9698001db650fa6262ae4ee/src/ingameWindows/iwPostWindow.cpp#L69
A line that is almost the same as the surrounding ones, but the only one that
got that call attributed.

I was not able to create a mini-example with this behaviour as clang coverage
works in almost all other cases, especially trivial ones.

I attach the raw gcov file (llvm-cov gcov  --dump), just search for
"__cxx_global_array_dtor"

-- 
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 28770] New: Cannot select: v4f64 = X86ISD::SUBV_BROADCAST

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28770

Bug ID: 28770
   Summary: Cannot select: v4f64 = X86ISD::SUBV_BROADCAST
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Backend: X86
  Assignee: unassignedb...@nondot.org
  Reporter: i...@azulsystems.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Created attachment 16837
  --> https://llvm.org/bugs/attachment.cgi?id=16837&action=edit
Test case

LLVM fails with:

$ llc test.ll

LLVM ERROR: Cannot select: 0x7fe4c4082730: v4f64 = X86ISD::SUBV_BROADCAST
0x7fe4c4082500
  0x7fe4c4082500: v2f64,ch = load 0x7fe4c3c0cfd0,
0x7fe4c4082340, undef:i64
0x7fe4c4082340: i64 = add 0x7fe4c4081e70, Constant:i64<8>
  0x7fe4c4081e70: i64,ch = CopyFromReg 0x7fe4c3c0cfd0, Register:i64 %vreg0
0x7fe4c4081e00: i64 = Register %vreg0
  0x7fe4c4081fc0: i64 = Constant<8>
0x7fe4c40821f0: i64 = undef
In function: test

Reverting this change: https://reviews.llvm.org/D22460 allows test to pass.

-- 
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 28771] New: InstSimplify crashes on trivial bitcast

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28771

Bug ID: 28771
   Summary: InstSimplify crashes on trivial bitcast
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: es...@apple.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

define <2 x i32> @test() {
  %tmp6 = bitcast <4 x half> 
to <2 x i32>
  ret <2 x i32> %tmp6
}

Assertion failed: (C->getType()->isIntOrIntVectorTy() && "ZEXt operand must be
integral"), function getZExt, file ../lib/IR/Constants.cpp, line 1598.
Stack dump:
0.Program arguments: bin/opt -instsimplify -S 
1.Running pass 'Function Pass Manager' on module ''.
2.Running pass 'Remove redundant instructions' on function '@test'

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


[llvm-bugs] [Bug 28613] stage2 bootstrap crashes after r273585

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28613

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #5 from Hans Wennborg  ---
Nirav committed r277135 which should have fixed this.

Ismail: can you please verify and re-open otherwise?

-- 
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 28600] [meta] 3.9.0 Release Blockers

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28600

Bug 28600 depends on bug 28613, which changed state.

Bug 28613 Summary: stage2 bootstrap crashes after r273585
https://llvm.org/bugs/show_bug.cgi?id=28613

   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 28749] heap-use-after-free in SelectionDAG

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28749

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #2 from Hans Wennborg  ---
Nirav's r277135 seems to have fixed this.

-- 
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 28690] linker script: implement EXCLUDE_FILE

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28690

ema...@freebsd.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
   Assignee|unassignedb...@nondot.org   |dav...@freebsd.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


[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=23214

Bug 23214 depends on bug 28690, which changed state.

Bug 28690 Summary: linker script: implement EXCLUDE_FILE
https://llvm.org/bugs/show_bug.cgi?id=28690

   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 28604] Crash in MachineBlockPlacement

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28604

Haicheng Wu  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||haich...@codeaurora.org
 Resolution|--- |DUPLICATE

--- Comment #1 from Haicheng Wu  ---


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

-- 
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 28772] New: libcxx's string_view breaks C++11 code (r276238)

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28772

Bug ID: 28772
   Summary: libcxx's string_view breaks C++11 code (r276238)
   Product: libc++
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: v...@apple.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
Classification: Unclassified

The following code breaks when compiled with ToT clang+libcxx using -std=c++11:

```
#include 

int main() {
  std::string A = "Hello";
  const char *B = "world";
  A.assign(B, 0, 1);
  return 0;
}
```

There is an ambiguous implicit conversion:

```
  A.assign(B, 0, 1);
  ~~^~
/Users/vk/Desktop/llvm/build/bin/../include/c++/v1/string:966:19: note:
candidate function
basic_string& assign(const basic_string& __str, size_type __pos, size_type
__n=npos);
  ^
/Users/vk/Desktop/llvm/build/bin/../include/c++/v1/string:968:19: note:
candidate function
basic_string& assign(__self_view __sv, size_type pos, size_type n=npos);
```

This has broken our internal arm test suite.

I suspect this was caused by libcxx/r276238. I don't think this functionality
should break C++11 code.

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


[llvm-bugs] [Bug 28771] InstSimplify crashes on trivial bitcast

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28771

David Majnemer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||david.majne...@gmail.com
 Resolution|--- |FIXED
   Assignee|unassignedb...@nondot.org   |david.majne...@gmail.com

--- Comment #1 from David Majnemer  ---
Fixed in r277197.

-- 
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 28738] fmod and similar method static_assert on aix

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28738

Xing Xue  changed:

   What|Removed |Added

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

--- Comment #3 from Xing Xue  ---
Hi Eli,  You are right, the AIX  defines these overload functions and
that is the reason why they are excluded here.  AIX guards those functions with
#if !defined(__COMPATMATH__) and the originator of this bug's compiler happens
to define the macro.  As per discussion with the originator, I will enable
these definitions in LLVM's  for AIX.

-- 
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 28756] Xbox Tech 1 855 338 0710 Xbox Customer Support Number

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28756

Tanya Lattner  changed:

   What|Removed |Added

 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


[llvm-bugs] [Bug 28592] clang-3.7 @3.7.1_3+analyzer segfault -- MacOSX 10.6.8 with libc++

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28592

Lawrence Velázquez  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||v...@larryv.me
 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 28770] Cannot select: v4f64 = X86ISD::SUBV_BROADCAST

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28770

Simon Pilgrim  changed:

   What|Removed |Added

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

--- Comment #5 from Simon Pilgrim  ---
Fixed in rL277214 - sorry about that Igor!

-- 
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 28473] GCC Compatibility: __final specifier unsupported

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28473

Erich Keane  changed:

   What|Removed |Added

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

--- Comment #2 from Erich Keane  ---
Fixed in revision https://reviews.llvm.org/rL277134 with
https://reviews.llvm.org/rL277206 as a memory-safety fix.

-- 
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 28773] New: Assertion `(!ModifiedMF || EmitDone) && "Dbg values are not emitted in LDV"' with fast-isel and greedy regalloc

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28773

Bug ID: 28773
   Summary: Assertion `(!ModifiedMF || EmitDone) && "Dbg values
are not emitted in LDV"' with fast-isel and greedy
regalloc
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: Common Code Generator Code
  Assignee: unassignedb...@nondot.org
  Reporter: eli.fried...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Created attachment 16841
  --> https://llvm.org/bugs/attachment.cgi?id=16841&action=edit
Testcase

"llc -O0 -regalloc=greedy a.ll" crashes with the attached .ll file.  On x86-64
Linux if it matters.

I hand-edited the attached IR to insert an extra call to llvm.dbg.value, so
it's possible the debug info is invalid somehow, but I think it's okay.

-- 
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 28774] New: MIR parsing of BranchProbability is broken

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28774

Bug ID: 28774
   Summary: MIR parsing of BranchProbability is broken
   Product: tools
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: llc
  Assignee: unassignedb...@nondot.org
  Reporter: d.c.d...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

The branch probability is printed as e.g. "successors:
%bb.2.for.body(0x7c00 / 0x8000 = 96.88%)" by BranchProbability.cpp:31:

OS << format("0x%08" PRIx32 " / 0x%08" PRIx32 " = %.2f%%", N, D, Percent);

But this is parsed by MIParser.cpp:463 as:

if (consumeIfPresent(MIToken::lparen)) {
  if (Token.isNot(MIToken::IntegerLiteral))
return error("expected an integer literal after '('");
  if (getUnsigned(Weight))
return true;
  lex();
  if (expectAndConsume(MIToken::rparen))
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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 28775] New: LLD failed to link LLDB executable

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28775

Bug ID: 28775
   Summary: LLD failed to link LLDB executable
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedb...@nondot.org
  Reporter: eugene.zele...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

I tried to use LLD as linker for LLDB project with recently introduced CMake's
option -DLLVM_ENABLE_LLD=ON.  I also used -DLLVM_ENABLE_LIBCXX=ON.

I tried to build trunk as of r277163.

[ 89%] Linking CXX executable ../../bin/lldb
undefined symbol: _ZN4lldb10SBDebugger10InitializeEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger11SetUseColorEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger15GetInstanceNameEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger16GetVersionStringEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger16SetTerminalWidthEj in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger16SkipAppInitFilesEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger17SkipLLDBInitFilesEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger18GetErrorFileHandleEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger18SetCloseInputOnEOFEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger18SetErrorFileHandleEP8_IO_FILEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger18SetInputFileHandleEP8_IO_FILEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger19GetOutputFileHandleEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger19SetOutputFileHandleEP8_IO_FILEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger20GetScriptingLanguageEPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger20SetUseExternalEditorEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger21GetCommandInterpreterEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger21RunCommandInterpreterEbb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol:
_ZN4lldb10SBDebugger21RunCommandInterpreterEbbRNS_30SBCommandInterpreterRunOptionsERiRbS4_
in CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger22DispatchInputInterruptEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger22GetDefaultArchitectureEPcm in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger22SaveInputTerminalStateEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger22SetDefaultArchitectureEPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger24GetInternalVariableValueEPKcS2_ in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger25RestoreInputTerminalStateEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger6CreateEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger7DestroyERS0_ in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger7RunREPLENS_12LanguageTypeEPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger8GetAsyncEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger8SetAsyncEb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebugger9TerminateEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBDebuggerD1Ev in CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBFileSpec19AppendPathComponentEPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBFileSpec25ResolveExecutableLocationEv in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBFileSpecC1EPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBFileSpecC1EPKcb in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb10SBFileSpecD1Ev in CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb12SBStringList16GetStringAtIndexEm in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb12SBStringListD1Ev in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb13SBBroadcasterC2EPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb13SBBroadcasterD2Ev in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb17SBLanguageRuntime25GetLanguageTypeFromStringEPKc in
CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol:
_ZN4lldb20SBCommandInterpreter24GetArgumentTypeAsCStringENS_19CommandArgumentTypeE
in CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol:
_ZN4lldb20SBCommandInterpreter29SourceInitFileInHomeDirectoryERNS_21SBCommandReturnObjectE
in CMakeFiles/lldb.dir/Driver.cpp.o
undefined symbol: _ZN4lldb20SBC

[llvm-bugs] [Bug 28774] MIR parsing of BranchProbability is broken

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28774

David Majnemer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||david.majne...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #1 from David Majnemer  ---


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

-- 
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 28776] New: Warn for implicit conversion from char literal to int

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28776

Bug ID: 28776
   Summary: Warn for implicit conversion from char literal to int
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: da...@doublewise.net
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

This is related to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55254&list_id=139817

I sometimes want to construct a string with n copies of a char c. However, I
frequently get the order of elements in the constructor mixed up. Rather than
saying std::string(80, '='), I accidentally call std::string('=', 80). If I go
through the trouble to put something in single quotes, I probably mean to pass
it to something expecting a char, not an integer.

Ultimately, I want to get a warning for this code:


#include 

int main() {
std::string const probably_wrong('0', 80);
}

-- 
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 28777] New: Warn for std::string constructor with wrong size

2016-07-29 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28777

Bug ID: 28777
   Summary: Warn for std::string constructor with wrong size
   Product: libc++
   Version: 3.8
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: da...@doublewise.net
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
Classification: Unclassified

This is the same bug in gcc reported here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54924&list_id=139817


The constructor for std::string that takes a pointer to an array of char and a
size assumes that the array of char you pass in is at least as large as the
size you specify. In other words, std::string str("0", 100) is undefined
behavior. The real issue can be much more subtle if escape characters are
involved:

// Construct a string alternating a literal '0' with a null character '\0'
std::string str("0\00\00\00\00\0", 10);

It would be nice if there were some way to warn that the size argument passed
in does not match the array (pointer) argument.

I don't know exactly which component this bug should be filed against. It seems
that clang needs to provide some sort of ability to annotate that an integer
parameter is the size of a pointer (array) parameter, and then libc++ needs to
use this annotation on std::string so that clang can provide the warning. I do
not know if this infrastructure exists.

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