[llvm-bugs] [Bug 30732] neon instructions emitted for targets without it.

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30732

James Molloy  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||james.mol...@arm.com
 Resolution|--- |INVALID

--- Comment #1 from James Molloy  ---
Hi,

NEON is indeed optional for ARMv7-A cores, however it is on by default. It is
possible to disable NEON by specifying the -mfpu option to a VFP unit (not
"neon"):

./bin/clang --target=arm-linux-unknown-gnueabihf -march=armv7-a -mcpu=generic
-O2 x.c -o - -S -mfpu=vfpv3
... snip ...
vldrd0, .LCPI0_0
... snip ...

-- 
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 30728] Cannot build with -DLIBOMP_OMP_VERSION=40

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30728

Paul Osmialowski  changed:

   What|Removed |Added

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

--- Comment #2 from Paul Osmialowski  ---
Seems like it was being fixed as I opened this ticket.

-- 
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 30489] Cannot build with -DLIBOMP_FORTRAN_MODULES=True

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30489

Paul Osmialowski  changed:

   What|Removed |Added

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

--- Comment #2 from Paul Osmialowski  ---
Fixed upstream.

-- 
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 30733] New: section flags syntax differences between gas and llvm intergrated assembler

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30733

Bug ID: 30733
   Summary: section flags syntax differences between gas and llvm
intergrated assembler
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: christof.do...@arm.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

gas its .section directive nowadays accepts "a numeric value indicating the
bits to be set in the ELF section header's flags field". See:

https://sourceware.org/binutils/docs-2.27/as/Section.html#Section

Note that this can also be applied to builtin sections. For example this works
in gas (but not in llvm):
.section .text,"0x2006",%progbits

-- 
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 30734] New: Building with CFLAGS=-DBUILD_MEMORY=1 (FIRST_TOUCH) does not export non-static __kmp_ft_page_allocate() function into a final library

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30734

Bug ID: 30734
   Summary: Building with CFLAGS=-DBUILD_MEMORY=1 (FIRST_TOUCH)
does not export non-static __kmp_ft_page_allocate()
function into a final library
   Product: OpenMP
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Runtime Library
  Assignee: unassignedb...@nondot.org
  Reporter: pawel.osmialow...@foss.arm.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

I guess following is missing in kmp.h:

#if (BUILD_MEMORY==FIRST_TOUCH)
extern void * __kmp_ft_page_allocate( size_t size );
#endif

...somewhere before this:

extern void * ___kmp_page_allocate( size_t size KMP_SRC_LOC_DECL );

-- 
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 30735] New: llvm-cov timeout in buildbots may be caused by Unix signal implementation

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30735

Bug ID: 30735
   Summary: llvm-cov timeout in buildbots may be caused by Unix
signal implementation
   Product: new-bugs
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: renato.go...@linaro.org
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Timeouts on check-all are getting slightly more common than they should.
Example:

http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/15968

and many other PPC and AArch64 builds out there.

While building it locally on AArch64, I noticed my tests were locked in the
same way as we saw the buildbot once, with multiple instances of `llvm-cov` and
zero CPU utilisation.

Here's a few error messages I've seen on my local build (that weren't on the
buildbots, possibly because the timeout killed it first):

terminate called after throwing an instance of 'std::system_error'
  what():  Unknown error -1
#0 0x83f2e8ec llvm::sys::PrintStackTrace(llvm::raw_ostream&)
llvm/lib/Support/Unix/Signals.inc:402:0

I'm not sure this is related, but it sure it weird, given that those errors
weren't on `llvm-cov` itself, but on unrelated unit tests, like
`VerifierTest.StripInvalidDebugInfoLegacy`.

-- 
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 28752] Assertion `Parent->isHidden() && "unexpectedly hidden decl"' failed.

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28752

Vassil Vassilev  changed:

   What|Removed |Added

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

--- Comment #6 from Vassil Vassilev  ---
Another fix was done in r284577. The bug should be fixed 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 30736] New: LLVM fails to load DIA from VS 2015 on clang-x64-ninja-win7 bot

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30736

Bug ID: 30736
   Summary: LLVM fails to load DIA from VS 2015 on
clang-x64-ninja-win7 bot
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: DebugInfo
  Assignee: unassignedb...@nondot.org
  Reporter: r...@google.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Example:
http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/builds/16588

All the tools that use DIA print empty error messages like this: "llvm-pdbdump:
DIA Error: "

First, we should fix the bot. Second, it would be nice if our build was less
fragile to DIA registration issues.

-- 
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 30737] New: Half-baked clang warning about address of members of packed structs

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30737

Bug ID: 30737
   Summary: Half-baked clang warning about address of members of
packed structs
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: st...@mit.edu
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Created attachment 17461
  --> https://llvm.org/bugs/attachment.cgi?id=17461&action=edit
Minimal test case with actual code from production

I'm using clang 4.0 on Debian and getting spurious "address-of-packed-member"
warnings.

The struct in question is declared with 

  __attribute__((packed))
  __attribute__((aligned(2)))

and consists of three unsigned shorts. 

So it seems the warning is triggering without regard to the actual alignment of
the struct and its members and without regard to the actual storage aligment of
the struct. 



$ /usr/bin/clang-4.0 -v 
clang version 4.0.0-svn283054-1~exp1 (trunk)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/5.4.1
Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/6.2.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.1
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6.2.0
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.1
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.2.0
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.1
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/bin/../lib/gcc/x86_64-linux-gnu/6.2.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
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 30498] [asan] Find a better way to print variables in stack-use-after-scope reports

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30498

Vitaly Buka  changed:

   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 28837] [ThinLTO] Comdat declaration rejected by Verifier during ThinLTO link

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=28837

Wolfgang Pieb  changed:

   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 30706] Fatal crash when targeting thumbv7-windows-msvc

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30706

Reid Kleckner  changed:

   What|Removed |Added

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

--- Comment #7 from Reid Kleckner  ---
r284633

-- 
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 30739] New: assertion failure on ambiguous qualifier in dependent member access, "Cannot handle ambiguities here yet"

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30739

Bug ID: 30739
   Summary: assertion failure on ambiguous qualifier in dependent
member access, "Cannot handle ambiguities here yet"
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: richard-l...@metafoo.co.uk
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

Testcase:

inline namespace N { struct X { int n; }; }
inline namespace M { struct X {}; }
struct Y : N::X {};
template int f(T y) { return y.X::n; }

Result:

clang-3.5: lib/Sema/SemaCXXScopeSpec.cpp:370: clang::NamedDecl
*clang::Sema::FindFirstQualifierInScope(clang::Scope *,
clang::NestedNameSpecifier *): Assertion `!Found.isAmbiguous() && "Cannot
handle ambiguities here yet"' failed.

-- 
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 30478] UBSan vptr: false positive if virtual method if privately overriden

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30478

Vedant Kumar  changed:

   What|Removed |Added

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

--- Comment #2 from Vedant Kumar  ---
Fixed in clang/r284636.

-- 
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 30740] New: -fsanitize-blacklist not working to support MSAN warnings

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30740

Bug ID: 30740
   Summary: -fsanitize-blacklist not working to support MSAN
warnings
   Product: compiler-rt
   Version: 3.9
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: compiler-rt
  Assignee: unassignedb...@nondot.org
  Reporter: d...@mapbox.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

I've been trying to use `-fsanitize=memory
-fsanitize-blacklist=msan-blacklist.txt` together. I would expect that the
WARNINGS I suppress in the `msan-blacklist.txt` file using `fun:` and `src:`
syntax would be respected (I am following the doc at
http://clang.llvm.org/docs/SanitizerSpecialCaseList.html). However what I am
seeing is that the WARNINGS I am trying to suppress still show up. I am unable
to suppress them.

I'm testing with clang 3.9.0. Did support for suppressions regress?

-- 
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 30731] Assertion `CXXInfo->BaseOffsets.count(Base) && "Did not find base!"' failed

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30731

Hans Wennborg  changed:

   What|Removed |Added

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

--- Comment #3 from Hans Wennborg  ---
r284624

-- 
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 30741] New: Issue parsing linker script

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30741

Bug ID: 30741
   Summary: Issue parsing linker script
   Product: lld
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedb...@nondot.org
  Reporter: b...@comstyle.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

ld.lld -T ../../../../arch/amd64/conf/ld.script -X --warn-common -nopie -S -o
bsd ${SYSTEM_HEAD} vers.o ${OBJS}
line 52: ; expected, but got &
__text_start = ABSOLUTE(.) & 0xf000;
 ^

The linker script can be seen here..

http://openbsd.comstyle.com/cgi/cvsweb/src/sys/arch/amd64/conf/ld.script

-- 
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 30741] Issue parsing linker script

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30741

Rui Ueyama  changed:

   What|Removed |Added

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

--- Comment #1 from Rui Ueyama  ---
Should be fixed in r284662.

-- 
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 30742] New: loop vectorizer causes dominance violation

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30742

Bug ID: 30742
   Summary: loop vectorizer causes dominance violation
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: eric.schwe...@pgroup.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

Created attachment 17462
  --> https://llvm.org/bugs/attachment.cgi?id=17462&action=edit
-loop-vectorize bug

The attached program shows a failure in opt's loop vectorizer pass. I believe
this failure has been present for several releases, and I have replicated it
with trunk, 3.9, etc.

% opt bug.bc -verify -disable-output
% opt bug.bc -loop-vectorize -disable-output
Instruction does not dominate all uses!
  %49 = select i1 %48, i32 1, i32 %47
  %43 = add i32 %49, -7
LLVM ERROR: Broken function found, compilation aborted!

-- 
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 30743] New: entry symbol start_phys not found, assuming 0

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30743

Bug ID: 30743
   Summary: entry symbol start_phys not found, assuming 0
   Product: lld
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedb...@nondot.org
  Reporter: b...@comstyle.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified

ld.lld -T ../../../../arch/amd64/conf/ld.script -X --warn-common -nopie -S -o
bsd ${SYSTEM_HEAD} vers.o ${OBJS}
entry symbol start_phys not found, assuming 0

The linker script can be seen here..

http://openbsd.comstyle.com/cgi/cvsweb/src/sys/arch/amd64/conf/ld.script

-- 
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 30640] [ppc] Shorter sequence to load 64bit constant with same hi/lo parts

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30640

Carrot  changed:

   What|Removed |Added

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

--- Comment #2 from Carrot  ---
Fixed in r284276.

-- 
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 30743] entry symbol start_phys not found, assuming 0

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30743

Rui Ueyama  changed:

   What|Removed |Added

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

--- Comment #1 from Rui Ueyama  ---
Fixed in r284676.

-- 
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 30744] New: Compile error in libclang/CIndex.cpp

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30744

Bug ID: 30744
   Summary: Compile error in libclang/CIndex.cpp
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: libclang
  Assignee: unassignedclangb...@nondot.org
  Reporter: d...@mapbox.com
CC: kli...@google.com, llvm-bugs@lists.llvm.org
Classification: Unclassified

With latest head (llvm https://llvm.org/svn/llvm-project/cfe/trunk@284684
91177308-0d34-0410-b5e6-96231b3b80d8) (clang
https://llvm.org/svn/llvm-project/cfe/trunk@284683
91177308-0d34-0410-b5e6-96231b3b80d8) I'm seeing:


../tools/clang/tools/libclang/CIndex.cpp:3160:3: error: use of undeclared
identifier 'LLVM_FUNCTION_NAME'
  LOG_FUNC_SECTION {
  ^
../tools/clang/tools/libclang/CLog.h:101:38: note: expanded from macro
'LOG_FUNC_SECTION'
#define LOG_FUNC_SECTION LOG_SECTION(LLVM_FUNCTION_NAME)
 ^

-- 
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 26964] CodeGen compiler error

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=26964

Dane Springmeyer  changed:

   What|Removed |Added

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

--- Comment #1 from Dane Springmeyer  ---
No longer seeing this problem, marking as resolved.

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


[llvm-bugs] [Bug 30708] wrong code at -O3 on x86_64-linux-gnu (in both 32-bit and 64-bit modes)

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30708

Davide Italiano  changed:

   What|Removed |Added

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

--- Comment #8 from Davide Italiano  ---
This code exhibits undefined behaviour.

Just before instcombine (but after inlining and other many passes) main()
contains the following basica block:

.split:   ; preds = %0
  %cmp.i.us20 = icmp ugt i32 53, 1
  %shr.i.us21 = lshr i32 1, 53
  %cmp624.i.us22 = zext i1 %cmp.i.us20 to i32
  %conv4.i.us23 = or i32 %cmp624.i.us22, %shr.i.us21
  %. = select i1 %tobool8.us46.i, i32 0, i32 1
  store i32 1, i32* @c, align 4
  store i32 %., i32* @a, align 4
  store i32 %conv4.i.us23, i32* @b, align 4
  %tmp = load i32, i32* @b, align 4
  call void (i8*, ...) @printf(i8* getelementptr inbounds ([4 x i8], [4 x i8]*
@.str, i32 0, i32 0), i32 %tmp)
  ret void

This instruction:
  %shr.i.us21 = lshr i32 1, 53
has UB as we're trying to shift right > 32, that gets folded into `undef` by
instcombine, and the next `or i32 %cmp624.i.us22 undef` gets in turn folded
into -1. That's the `-1` value that's subsequently stored, loaded, and printed.

-- 
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 30708] wrong code at -O3 on x86_64-linux-gnu (in both 32-bit and 64-bit modes)

2016-10-19 Thread via llvm-bugs
https://llvm.org/bugs/show_bug.cgi?id=30708

Zhendong Su  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |---

--- Comment #9 from Zhendong Su  ---
Hi Davide, please note that original test program in C is valid, so, reopening
it.  And thanks for your effort in investigating it!

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