[llvm-bugs] [Bug 26126] New: Assertion failed! - Expression: !Init->isValueDependent()

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26126

Bug ID: 26126
   Summary: Assertion failed! -  Expression:
!Init->isValueDependent()
   Product: clang
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: steffen.dedek...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

Using CLANG 3.8.0 via ELLC.
Trying to compile a snippet using the Eigen3 library. 
Target: aarch64

I created this bug because I'm not sure if this duplicates
https://llvm.org/bugs/show_bug.cgi?id=12779

-- 
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 12726] Breakpoint not set at the prologue_end location in case of ARM.

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=12726

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |FIXED

--- Comment #2 from Renato Golin  ---
This has been 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 13139] Really long IR labels generated for gold/arm.cc -O3 (no limit to IR label length)

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=13139

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |INVALID

--- Comment #1 from Renato Golin  ---
This didn't seem to be a big deal back then, and wasn't picked up by any one so
far, so it's probably not an issue. 

I can't say I've ever had to worry about label sizes in IR, mostly because IR
is just a developer dump, not a production tool.

If anything, it'd be better focusing on tools that can work seamlessly with IR
(diffs, displays, refactoring) instead of making IR more palatable to human
eyes or to gain 1% speed on a purely developer tool.

-- 
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 13336] ARM NEON intrinsic vshlq_n_u64 fail on shifts over 7.

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=13336

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |FIXED

--- Comment #1 from Renato Golin  ---
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 16315] Apple clang 4.2 based on llvm 3.2 produces a wrong "instruction requires:arm-mode" ‏

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=16315

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |FIXED

--- Comment #2 from Renato Golin  ---
Seems to be working now...

$ cat asm.s
.thumb
add r2, pc, r2

$ llvm-mc -triple thumbv4t-none-eabi asm.s -filetype=obj -o asm.o

$ llvm-objdump -triple thumbv4t-none-eabi -d asm.o
Disassembly of section .text:
$t.0:
   0:7a 44 addr2, pc

-- 
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 16364] LLVMARMCodeGen project do not compile on VS 2012

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=16364

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |WORKSFORME

--- Comment #2 from Renato Golin  ---
I believe this was a momentary/local bug. We have plenty of Windows buildbots
building ARM. Unless more info is shared, there's nothing to do.

-- 
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 17045] ICE with 64-bit __sync_val_compare_and_swap on ARM

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=17045

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 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 26127] New: miscompilation with -O wrong branch taken

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26127

Bug ID: 26127
   Summary: miscompilation with -O wrong branch taken
   Product: clang
   Version: 3.7
  Hardware: PC
OS: Linux
Status: NEW
  Severity: release blocker
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: vasilis.vlachou...@cern.ch
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

In my program that compiles and runs with gcc with clang++ 3.7 on Fedora 23 it
fails on the following fraction of the code.

if (Abs(g) < Abs(f)) {
c1 = 0.0;
c4 = -c / (2.0*f);
} else {
c1 = -c / (2.0*g);
c4 = 0.0;
}

with g=-0.5, f=0.0  (doubles)
however it selects the upper branch and it makes a division by zero when
evaluating the c4.
When I switch off optimization it runs with no problem.
When I add a
printf("g=%g f=%g\n",g,f);
it also runs with no problem.

The Abs() is declared as
/* --- Abs --- */
template 
inline T Abs(const T& a) {
return (a<0) ? -a : a;
}
#include 
// Partial specializations
template <>
inline double Abs(const double& a) {
return fabs(a);
}
template <>
inline float Abs(const float& a) {
return fabsf(a);
}

I've tried to extract only the portion of the code that crashes, but all my
attempts failed. I can only reproduce it with the whole code.

In case it is necessary I can provide you the svn to download the code and a
test example.

-- 
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 19445] clang generating mov r0, r1 for thumb ISA v4T, v5TE

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=19445

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |INVALID

--- Comment #1 from Renato Golin  ---
Actually, the GNU assembler does accept that and encodes as "adds r0, r1, #0",
as documented by the original ARMv5 manual. Unless we have a source code and a
compiler command line with the output clearly failing on current GNU binutils,
there's nothing more to do.

-- 
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 12990] Implement sseregparm calling convention for x86_32 as supported by gcc

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=12990

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@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 19781] Clang crashed while parsing __visibility__ attribute under arm-linux-gnueabihf

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=19781

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |FIXED

--- Comment #1 from Renato Golin  ---
libc++ is compiling on its own and together with Clang on ARM and AArch64 for a
while 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 13796] Missing __ARM_PCS_VFP symbol on arm hard-float system causes error

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=13796

Renato Golin  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||renato.go...@linaro.org
 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 26128] New: libcxx fails to compile with newlib for cmath functions

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26128

Bug ID: 26128
   Summary: libcxx fails to compile with newlib for cmath
functions
   Product: libc++
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: rianqu...@gmail.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
Classification: Unclassified

In libcxx/include/cmath, use see the following:

...
using ::isinf;
using ::isnan;
...

In NewLib, these functions are macros. Here is a comment from the NewLib
source:

/* Note: isinf and isnan were once functions in newlib that took double
 *   arguments.  C99 specifies that these names are reserved for macros
 *   supporting multiple floating point types.  Thus, they are
 *   now defined as macros.  Implementations of the old functions
 *   taking double arguments still exist for compatibility purposes
 *   (prototypes for them are in ).  */

Currently I am patching libcxx with #ifndef _NEWLIB_VERSION wrapped around a
couple of these functions (there are several that have this issue). Not sure
what the correct solution would be, but this seems reasonable to me. 

- Rian

-- 
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 26129] New: [Mips] backend emits JAL instructions truncating the jump address

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26129

Bug ID: 26129
   Summary: [Mips] backend emits JAL instructions truncating the
jump address
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: d...@codeplay.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Hi,

when invoking a function through an absolute address, the mips backend emits
the JAL instruction. This is fine only when the address happens to be in the
same "PC-region branch", as the most significant part of the address is based
on the PC. Otherwise truncation happens and the behaviour is incorrect.

Repro, consider this snippet:

define i32 @foo(i32 signext %a, i32 signext %b) #0 {
  %1 = tail call i32 inttoptr (i32 1073741824 to i32 (i32, i32)*)(i32 signext
%a, i32 signext %b) #1
  ret i32 0
}

obtained by clang --target=mipsel--linux-android -O2 -c -emit-llvm -o sample.bc
sample.c 

int foo(int a, int b){
int (*f) (int, int) = (int (*) (int, int)) 0x4000; // 1 Gb
f(a, b); // Jumps to 0!
return 0;
}

Compile with llc -filetype=obj -mtriple=mipsel--linux-android sample.bc -o
sample.o:
Disassembly of section .text:
foo:
   0:e8 ff bd 27 addiu$sp, $sp, -24
   4:14 00 bf af sw$ra, 20($sp)
   8:00 00 00 0c jal0 // boom
   c:00 00 00 00 nop
  10:00 00 02 24 addiu$2, $zero, 0
  14:14 00 bf 8f lw$ra, 20($sp)
  18:08 00 e0 03 jr$ra
  1c:18 00 bd 27 addiu$sp, $sp, 24

This is a bug being around for some time affecting the JIT capability of LLDB
for Mips.

-- 
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 18864] llvm 3.5 fails to compile inline assembler on ARM

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=18864

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |FIXED

--- Comment #5 from Renato Golin  ---
Works on trunk.

-- 
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 26129] [Mips] backend emits JAL instructions truncating the jump address

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26129

Daniel Sanders  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||daniel.sand...@imgtec.com
 Resolution|--- |FIXED

--- Comment #1 from Daniel Sanders  ---
Hi,

I fixed this a couple days ago in r257339. Feel free to re-open this ticket if
the problem still occurs for you.

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


[llvm-bugs] [Bug 21270] [AArch64] Clang incorrectly warns with %wX register constraints

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=21270

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 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 22178] crash while trying to compile arm neon intrinsics

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=22178

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |FIXED

--- Comment #3 from Renato Golin  ---
No crashes any more. Seems 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 26130] New: build error for unused local variable with incomplete type

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26130

Bug ID: 26130
   Summary: build error for unused local variable with incomplete
type
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: a...@linaro.org
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

A .c file containing "static const struct undefined_struct object;" with no
user of 'object' and no defintion for 'struct undefined_struct' produces a
warning and an error with clang:

test.c:1:38: warning: tentative definition of variable with internal linkage
has incomplete non-array type 'const struct undefined_struct'
[-Wtentative-definition-incomplete-type]
static const struct undefined_struct object;
 ^
test.c:1:21: note: forward declaration of 'struct undefined_struct'
static const struct undefined_struct object;
^
test.c:1:38: error: tentative definition has type 'const struct
undefined_struct' that is never completed
static const struct undefined_struct object;
 ^
test.c:1:21: note: forward declaration of 'struct undefined_struct'
static const struct undefined_struct object;
^
1 warning and 1 error generated.

This is inconsistent with gcc, which compiles the file without issuing any
warning, and that causes a build failure in one file of the linux-kernel
(drivers/staging/wilc1000/wilc_spi.c) that incorrectly has a variable
definition remaining after the type was removed. I have submitted a patch to
the kernel to remove that obviously unused variable, but it seems that issuing
a warning without the build error would be more consistent behavior for clang.
(gcc should probably also warn about 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 23432] [CRASH REPORT] BitcoinArmory caused this (3.4.1 compiles the same code fine)

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=23432

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 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 24100] Clang assumes that Cortex-M4 has an FPU by default

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=24100

Renato Golin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||renato.go...@linaro.org
 Resolution|--- |INVALID

--- Comment #2 from Renato Golin  ---
Yes, the defaults are different, but that's not a bug, it's a choice.

If you'd like soft-float ABI you can either set "-mfpu=none" or
"-mfloat-abi=soft" or "-msoft-float" when using Cortex-M4, or choose Cortex-M3
instead.

-- 
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 26131] New: clang-format needs more than 10GB virtual memory to format 700 Byte file

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26131

Bug ID: 26131
   Summary: clang-format needs more than 10GB virtual memory to
format 700 Byte file
   Product: clang
   Version: 3.7
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: sebastian.buchw...@kit.edu
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Classification: Unclassified

Created attachment 15619
  --> https://llvm.org/bugs/attachment.cgi?id=15619&action=edit
File that triggers the issue

clang-format uses a lot of memory when formatting the attached C file:
ulimit -v 10485760
lang-format-3.7 clangformat.c
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
...[stacktrace]

clang-format-3.7 -version
Ubuntu clang-format version 3.7.0-2ubuntu1 (tags/RELEASE_370/final) (based on
LLVM 3.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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 26134] New: VarDecl::checkInitIsIce() !Init->isValueDependent Assertion failure

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26134

Bug ID: 26134
   Summary: VarDecl::checkInitIsIce() !Init->isValueDependent
Assertion failure
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: saugust...@google.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

This looks quite similar to these bugs, but they have been marked fixed for a
while. So this is either a regression, or a new code path.

https://llvm.org/bugs/show_bug.cgi?id=13988
https://llvm.org/bugs/show_bug.cgi?id=14615

The following code and command line results in an assertion failure at inside a
debug copy of trunk:

clang++ orig.ii -std=gnu++11

template
struct PossiblyRotatingKernelHelper {};

template struct gebp_kernel {
  void f() { PossiblyRotatingKernelHelper
possiblyRotatingKernelHelper; }
  static const bool UseRotatingKernel = B;
};

clang-3.8:
/usr/local/google/home/saugustine/llvm/llvm/tools/clang/lib/AST/Decl.cpp:2181:
bool clang::VarDecl::checkInitIsICE() const: Assertion
`!Init->isValueDependent()' failed.



Incidentally, if I comment out this assertion, an identical one fires very soon
after, and if I comment out that one, another identical one fires very soon
after.

-- 
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 25973] basic_string::assign(InputIt, InputIt) doesn't provide the strong exception safety guarantee

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=25973

Marshall Clow (home)  changed:

   What|Removed |Added

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

--- Comment #7 from Marshall Clow (home)  ---
Fixed in revision 257682.

-- 
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 25944] Assertion `Type == RT64_32' failed while building Qt 5.6.0-beta

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=25944

Rafael Ávila de Espíndola  changed:

   What|Removed |Added

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

--- Comment #6 from Rafael Ávila de Espíndola  ---
In r257697 I converted the asserts into proper errors.

Of the error checks added, the only case gas doesn't produce an error for is
GOTPCREL. It is not clear why, the psabi says the field is 32 bits.

-- 
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 26135] New: Cortex-A5 codegen suboptimal?

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26135

Bug ID: 26135
   Summary: Cortex-A5 codegen suboptimal?
   Product: libraries
   Version: 3.7
  Hardware: Other
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Backend: ARM
  Assignee: unassignedb...@nondot.org
  Reporter: tulip...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

It seems code generation for Cortex-A5 and armv7 doesn't provide much benefit,
sometimes even coming out a little slower (compared to default and v6
respectively). 

Firstly, our old friend from issue #26106, w/o NEON and unrolling:

default cpu - v7, v6:

test sum_deque   ... bench:   5,219 ns/iter (+/- 56), 4,967 ns/iter (+/-
50)

test sum_deque_2 ... bench:   3,272 ns/iter (+/- 40), 3,112 ns/iter (+/-
22)

It seems v6 code is faster on this cpu.


Secondly a few benchmarks, where the cortex-a5 target is either equal or
slower. (4-core)

Spectral-norm benchmark, v7:
$ time ./spectral 5500

default cpucortex-a5

real0m9.106s real0m9.051s
user0m34.110suser0m34.240s
sys 0m0.040s sys 0m0.020s

Fannkuch benchmark:
$ time ./fannkuch 12

real0m30.017s real0m30.645s
user1m55.570s user1m56.350s
sys 0m0.030s  sys 0m0.010s


Command used to compile:
rustc -C opt-level=3 -C target-feature=+v7 -C target-cpu=cortex-a5

Those were just a few examples off the top of my head, probably not the best
ones. I'm sure I've also seen an example or two benefiting from the cortex-a5
target but can't remember which.

-- 
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 26085] r249995 causes premature diagnostics during Objective-C method lookup

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26085

George Burgess  changed:

   What|Removed |Added

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

--- Comment #2 from George Burgess  ---
Committed as r257710. Thanks for catching 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 26059] [meta] 3.8.0 Release Blockers

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26059

Bug 26059 depends on bug 26085, which changed state.

Bug 26085 Summary: r249995 causes premature diagnostics during Objective-C 
method lookup
https://llvm.org/bugs/show_bug.cgi?id=26085

   What|Removed |Added

 Status|ASSIGNED|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 21528] [Windows] Stack traces don't contain namespaces in function names since r220544

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=21528

Reid Kleckner  changed:

   What|Removed |Added

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

--- Comment #17 from Reid Kleckner  ---
Eventually fixed in r255744, r257658, and r257723.

-- 
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 26059] [meta] 3.8.0 Release Blockers

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26059

Bug 26059 depends on bug 26124, which changed state.

Bug 26124 Summary: [ms] Regression(256730): Miscompile in 32-bit code
https://llvm.org/bugs/show_bug.cgi?id=26124

   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 26124] [ms] Regression(256730): Miscompile in 32-bit code

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26124

David Majnemer  changed:

   What|Removed |Added

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

--- Comment #9 from David Majnemer  ---
Fixed in r257730.

-- 
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 26136] New: clang 3.8 branch openmp regressions

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26136

Bug ID: 26136
   Summary: clang 3.8 branch openmp regressions
   Product: OpenMP
   Version: unspecified
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: normal
  Priority: P
 Component: Clang Compiler Support
  Assignee: unassignedclangb...@nondot.org
  Reporter: howarth.mailing.li...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Current clang 3.8 branch exhibits a number of regressions in both the libomp
test suite and OpenMP3.1_Validation test suite that appeared to have been
introduced shortly before the branch occurred. The attached
test_omp_for_firstprivate-eb139a.sh and test_omp_for_firstprivate-eb139a.c
demonstrates one of these failures from the OpenMP3.1_Validation test suite on
x86_64-apple-darwin15.

-- 
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 26137] New: Warn when manual invoking a non-virtual destructor of a class with virtual methods

2016-01-13 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26137

Bug ID: 26137
   Summary: Warn when manual invoking a non-virtual destructor of
a class with virtual methods
   Product: clang
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: dch...@google.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

Clang already has a warning (-Wdelete-non-virtual-dtor) when deleting a class
with virtual functions but a non-virtual destructor. However, this warning
doesn't trigger when the destructor is manually invoked:

$ cat test.cc
#include 
#include 

struct B {
  ~B() { puts("Destroying B"); }
  virtual void f() = 0;
};

struct D : public B {
  ~D() { puts("Destroying D"); }
  void f() override { }
};

int main() {
  char buffer[sizeof(D)];
  B* b = new (buffer) D;
  b->~B();  // No warning.

  B* b2 = new D;
  delete b2;  // Warning.
}
$ clang++ -Wall -std=c++11 test.cc
test.cc:20:3: warning: delete called on 'B' that is abstract but has
non-virtual destructor
  [-Wdelete-non-virtual-dtor]
  delete b2;  // Warning.
  ^
1 warning generated.

This has already resulted in at least one real bug in Chrome:
https://crbug.com/577478.

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