[llvm-bugs] [Bug 34250] New: llvm-cov: Coverage summary shows coverage of instantiations even with -show-expansions=0
https://bugs.llvm.org/show_bug.cgi?id=34250 Bug ID: 34250 Summary: llvm-cov: Coverage summary shows coverage of instantiations even with -show-expansions=0 Product: new-bugs Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dennis.fels...@sap.com CC: llvm-bugs@lists.llvm.org Created attachment 19015 --> https://bugs.llvm.org/attachment.cgi?id=19015&action=edit Main cpp file, expect 100% line and region coverage here When creating an html report using llvm-cov show -format html -show-instantiations=0 -show-expansions=0, the summary html file still shows a lower line and region coverage for files containing a macro expansion. I would expect 100% line and region coverage for that file since we explicitly told llvm-cov that we don't care about expansions. -- 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 34251] New: ms-pdb: missing pdb for lib shouldn't be fatal
https://bugs.llvm.org/show_bug.cgi?id=34251 Bug ID: 34251 Summary: ms-pdb: missing pdb for lib shouldn't be fatal Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: alex-telis...@ya.ru CC: llvm-bugs@lists.llvm.org lld-link fails if you have external .lib file that was compiled with /DEBUG but don't have .pdb file for it. MSVC linker only warns about it and continues linking. -- 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 32942] Using threads slows down test/ELF/many-sections.s a lot
https://bugs.llvm.org/show_bug.cgi?id=32942 George Rimar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from George Rimar --- r311312, r311313 -- 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 34252] New: ms-pbd: link fails if two libs have .obj files with the same path
https://bugs.llvm.org/show_bug.cgi?id=34252 Bug ID: 34252 Summary: ms-pbd: link fails if two libs have .obj files with the same path Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: alex-telis...@ya.ru CC: llvm-bugs@lists.llvm.org `PDBLinker::addObjFile` function uses internal .obj path for identifier in case of .lib objects. That path can be identical for two different libs (I my case it happened while linking with qt with several plugins statically) and shouldn't be an error. -- 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 34253] New: Constant expression from permitted result of a constant expression is not constexpr
https://bugs.llvm.org/show_bug.cgi?id=34253
Bug ID: 34253
Summary: Constant expression from permitted result of a
constant expression is not constexpr
Product: clang
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: antosh...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
The following code fails to compile:
int main() {
static const char someVar[] = "str";
constexpr auto c0 = someVar[0];
}
error: constexpr variable 'c0' must be initialized by a constant expression
constexpr auto c0 = someVar[0];
^~~
This seems to be an error:
"In any constexpr variable declaration, the full-expression of the
initialization shall be a constant expression [expr.const]"
Where [expr.const] has the paragraphs:
"A constant expression is either a glvalue core constant expression that refers
to an entity that is a permitted result of a constant expression
An entity is a permitted result of a constant expression if it is an object
with static storage duration that is either not a temporary object "
--
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 34254] New: Clang misses an opportunity to evaluate a call to std::accumulate at compile time
https://bugs.llvm.org/show_bug.cgi?id=34254
Bug ID: 34254
Summary: Clang misses an opportunity to evaluate a call to
std::accumulate at compile time
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: jb...@me.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
The following code:
#include
#include
using std::begin;
using std::end;
int f()
{
int xs[32];
std::iota(begin(xs),
end(xs), 1);
return std::accumulate(begin(xs),
end(xs), 0);
}
Is compiled with gcc-trunk -O3 to:
f():
mov eax, 528
ret
whereas Clang evaluates the call to accumulate at compile time.
example at: https://godbolt.org/g/dd831y
This is not impeding my work in any way and was discovered by accident.
--
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 34255] New: llvm-cov: Coverage for destructors wrong with optimizations
https://bugs.llvm.org/show_bug.cgi?id=34255 Bug ID: 34255 Summary: llvm-cov: Coverage for destructors wrong with optimizations Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dennis.fels...@sap.com CC: llvm-bugs@lists.llvm.org Created attachment 19018 --> https://bugs.llvm.org/attachment.cgi?id=19018&action=edit Example code, compile with -O1 With -O0 the destructor is covered, while with -O1 and higher it is not. This forces me to run coverage code with -O0. Minimal example attached. I would expect the destructor to always be covered. -- 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 34256] New: clang segmentation fault for OpenMP target
https://bugs.llvm.org/show_bug.cgi?id=34256
Bug ID: 34256
Summary: clang segmentation fault for OpenMP target
Product: clang
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: siegmar.gr...@informatik.hs-fulda.de
CC: llvm-bugs@lists.llvm.org
loki introduction 119 llc -version
LLVM (http://llvm.org/):
LLVM version 5.0.0svn-r311291
Optimized build.
Default target: x86_64-unknown-linux-gnu
Host CPU: haswell
Registered Targets:
nvptx - NVIDIA PTX 32-bit
nvptx64 - NVIDIA PTX 64-bit
x86 - 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64
"libomptarget" is disabled at the moment, but nevertheless the compiler
shouldn't generate a segmentation fault. I've already reported the problem for
the trunk (Bug 34104) and I would be grateful if somebody can fix the error
before version 5.0 will be released. The program is available with Bug 34104.
loki introduction 119 clang -fopenmp -fopenmp-targets=nvptx64-nvidia-cuda
dot_prod_accelerator_OpenMP.c -lomptarget
clang-5.0: error: cannot find libdevice for . Provide path to different CUDA
installation via --cuda-path, or pass -nocudalib to build without linking with
libdevice.
#0 0x7f26ea2c3e0a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/usr/local/llvm-5.0/lib64/libLLVMSupport.so.5+0xfbe0a)
#1 0x7f26ea2c1f4e llvm::sys::RunSignalHandlers()
(/usr/local/llvm-5.0/lib64/libLLVMSupport.so.5+0xf9f4e)
#2 0x7f26ea2c2088 SignalHandler(int)
(/usr/local/llvm-5.0/lib64/libLLVMSupport.so.5+0xfa088)
#3 0x7f26ed3fdb10 __restore_rt (/lib64/libpthread.so.0+0x10b10)
#4 0x7f26ec6e2dd0
clang::driver::tools::NVPTX::Linker::ConstructJob(clang::driver::Compilation&,
clang::driver::JobAction const&, clang::driver::InputInfo const&,
llvm::SmallVector const&, llvm::opt::ArgList
const&, char const*) const
(/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0xc5dd0)
#5 0x7f26ec68318c
clang::driver::Driver::BuildJobsForActionNoCache(clang::driver::Compilation&,
clang::driver::Action const*, clang::driver::ToolChain const*, llvm::StringRef,
bool, bool, char const*, std::map, std::allocator >
>, clang::driver::InputInfo, std::less, std::allocator >
> >, std::allocator, std::allocator >
> const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind)
const (/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x6618c)
#6 0x7f26ec684b49
clang::driver::Driver::BuildJobsForAction(clang::driver::Compilation&,
clang::driver::Action const*, clang::driver::ToolChain const*, llvm::StringRef,
bool, bool, char const*, std::map, std::allocator >
>, clang::driver::InputInfo, std::less, std::allocator >
> >, std::allocator, std::allocator >
> const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind)
const (/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x67b49)
#7 0x7f26ec686992 void llvm::function_ref::callback_fn, std::allocator >
>, clang::driver::InputInfo, std::less, std::allocator >
> >, std::allocator, std::allocator >
> const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind)
const::{lambda(clang::driver::Action*, clang::driver::ToolChain const*, char
const*)#2}>(long, clang::driver::Action*, clang::driver::ToolChain const*, char
const*) (/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x69992)
#8 0x7f26ec66892c
clang::driver::OffloadAction::doOnEachDeviceDependence(llvm::function_ref const&)
const (/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x4b92c)
#9 0x7f26ec6824c9
clang::driver::Driver::BuildJobsForActionNoCache(clang::driver::Compilation&,
clang::driver::Action const*, clang::driver::ToolChain const*, llvm::StringRef,
bool, bool, char const*, std::map, std::allocator >
>, clang::driver::InputInfo, std::less, std::allocator >
> >, std::allocator, std::allocator >
> const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind)
const (/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x654c9)
#10 0x7f26ec684b49
clang::driver::Driver::BuildJobsForAction(clang::driver::Compilation&,
clang::driver::Action const*, clang::driver::ToolChain const*, llvm::StringRef,
bool, bool, char const*, std::map, std::allocator >
>, clang::driver::InputInfo, std::less, std::allocator >
> >, std::allocator, std::allocator >
> const, clang::driver::InputInfo> > >&, clang::driver::Action::OffloadKind)
const (/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x67b49)
#11 0x7f26ec6857db
clang::driver::Driver::BuildJobs(clang::driver::Compilation&) const
(/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x687db)
#12 0x7f26ec686789
clang::driver::Driver::BuildCompilation(llvm::ArrayRef)
(/usr/local/llvm-5.0/lib64/libclangDriver.so.5+0x69789)
#13 0x0040c643 (clang+0x40c643)
#14 0x7f26e7f676e5 __libc_start_main
/usr/src/debug/glibc-2.
[llvm-bugs] [Bug 34247] trunk/llvm/tools/clang/lib/Driver/ToolChains/Arch/Mips.cpp:235]: (style) Redundant condition:
https://bugs.llvm.org/show_bug.cgi?id=34247 Simon Atanasyan changed: What|Removed |Added Status|NEW |RESOLVED CC||si...@atanasyan.com Resolution|--- |FIXED --- Comment #1 from Simon Atanasyan --- Fixed at r311334. Thanks for the report. -- 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 34257] New: Loop unswitching stopped happening
https://bugs.llvm.org/show_bug.cgi?id=34257
Bug ID: 34257
Summary: Loop unswitching stopped happening
Product: libraries
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Loop Optimizer
Assignee: unassignedb...@nondot.org
Reporter: aivch...@gmail.com
CC: llvm-bugs@lists.llvm.org
foo.cpp:
int foo(bool x, int a) {
int s = a;
int i = 0;
while (i < 1) {
int y = x ? a : i;
s += y;
i++;
}
return s;
}
>clang++ foo.cpp -c -S -emit-llvm -o llvm_version.ll -O3
Before https://reviews.llvm.org/D35811 we used to nicely unswitch this loop:
define i32 @_Z12llvm_versionbi(i1 zeroext %x, i32 %a) local_unnamed_addr #0 {
entry:
%0 = mul i32 %a, 10001
%1 = add i32 %a, 49995000
%s.0.lcssa = select i1 %x, i32 %0, i32 %1
ret i32 %s.0.lcssa
}
I guess that degradation is expected, though, but, I'm not 100% sure
--
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 34253] Constant expression from permitted result of a constant expression is not constexpr
https://bugs.llvm.org/show_bug.cgi?id=34253 hst...@ca.ibm.com changed: What|Removed |Added Status|NEW |RESOLVED CC||hst...@ca.ibm.com Resolution|--- |INVALID --- Comment #1 from hst...@ca.ibm.com --- someVar[0] is not a core constant expression. It applies lvalue-to-rvalue conversion to a glvalue referring to a subobject, _of_ but not _being_ a complete non-volatile const object with a preceding initialization. See WG 21 document N 4687 subclause 8.20 [expr.const] bullet 2.7. -- 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 34255] llvm-cov: Coverage for destructors wrong with optimizations
https://bugs.llvm.org/show_bug.cgi?id=34255 Vedant Kumar changed: What|Removed |Added Status|NEW |RESOLVED CC||v...@apple.com Resolution|--- |WORKSFORME --- Comment #1 from Vedant Kumar --- I can't reproduce this issue. Mind sharing the exact compiler flags you're using, and the IR at both -O0 and -O1? At -O1, I see the counter increment for Bar's destructor inlined into main(): %3 = load i64, i64* getelementptr inbounds ([1 x i64], [1 x i64]* @__profc__ZN3BarD2Ev, i64 0, i64 0), align 8 %4 = add i64 %3, 1 store i64 %4, i64* getelementptr inbounds ([1 x i64], [1 x i64]* @__profc__ZN3BarD2Ev, i64 0, i64 0), align 8 -- 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 34098] [APFloat] DoubleAPFloat::isInteger would always trigger an assert.
https://bugs.llvm.org/show_bug.cgi?id=34098 Davide Italiano 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 33793] Move WholeProgramDevirt to new OptRemark API
https://bugs.llvm.org/show_bug.cgi?id=33793 Sam Elliott changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Sam Elliott --- https://reviews.llvm.org/rL311352 -- 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
https://bugs.llvm.org/show_bug.cgi?id=33789 Bug 33789 depends on bug 33793, which changed state. Bug 33793 Summary: Move WholeProgramDevirt to new OptRemark API https://bugs.llvm.org/show_bug.cgi?id=33793 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 34100] [APFloat] DoubleAPFloat::changeSign results in unusual values.
https://bugs.llvm.org/show_bug.cgi?id=34100 Davide Italiano changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |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 34258] New: clang crashes on valid code at -O3 running pass 'Aggressive Dead Code Elimination'
https://bugs.llvm.org/show_bug.cgi?id=34258
Bug ID: 34258
Summary: clang crashes on valid code at -O3 running pass
'Aggressive Dead Code Elimination'
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: s...@cs.ucdavis.edu
CC: llvm-bugs@lists.llvm.org
$ clang -v
clang version 6.0.0 (trunk 311306)
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 -O2 small.c; ./a.out
$
$ clang -O3 small.c
clang-6.0:
/tmp/llvm-builder/llvm-source-trunk/include/llvm/Support/GenericDomTreeConstruction.h:1030:
llvm::DomTreeBuilder::SemiNCAInfo::DeleteUnreachable(DomTreeT&,
llvm::DomTreeBuilder::SemiNCAInfo::BatchUpdatePtr,
llvm::DomTreeBuilder::SemiNCAInfo::TreeNodePtr)NodePtr,
llvm::DomTreeBuilder::SemiNCAInfo::NodePtr)> [with DomTreeT =
llvm::DominatorTreeBase;
llvm::DomTreeBuilder::SemiNCAInfo::NodePtr = llvm::BasicBlock*]:
Assertion `TN' failed.
#0 0x022a130a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/usr/local/clang-trunk/bin/clang-6.0+0x22a130a)
#1 0x0229f49e llvm::sys::RunSignalHandlers()
(/usr/local/clang-trunk/bin/clang-6.0+0x229f49e)
#2 0x0229f600 SignalHandler(int)
(/usr/local/clang-trunk/bin/clang-6.0+0x229f600)
#3 0x7f1b70198330 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x10330)
#4 0x7f1b6ef80c37 gsignal
/build/eglibc-SvCtMH/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0
#5 0x7f1b6ef84028 abort
/build/eglibc-SvCtMH/eglibc-2.19/stdlib/abort.c:91:0
#6 0x7f1b6ef79bf6 __assert_fail_base
/build/eglibc-SvCtMH/eglibc-2.19/assert/assert.c:92:0
#7 0x7f1b6ef79ca2 (/lib/x86_64-linux-gnu/libc.so.6+0x2fca2)
#8 0x01dd2627 unsigned int
llvm::DomTreeBuilder::SemiNCAInfo >::runDFS >::DeleteUnreachable(llvm::DominatorTreeBase&,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo*,
llvm::DomTreeNodeBase*)::{lambda(llvm::BasicBlock*,
llvm::BasicBlock*)#1}>(llvm::BasicBlock*, unsigned int,
llvm::DomTreeBuilder::SemiNCAInfo >::DeleteUnreachable(llvm::DominatorTreeBase&,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo*,
llvm::DomTreeNodeBase*)::{lambda(llvm::BasicBlock*,
llvm::BasicBlock*)#1}, unsigned int)
(/usr/local/clang-trunk/bin/clang-6.0+0x1dd2627)
#9 0x01dd43cf
llvm::DomTreeBuilder::SemiNCAInfo >::DeleteUnreachable(llvm::DominatorTreeBase&,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo*, llvm::DomTreeNodeBase*)
(/usr/local/clang-trunk/bin/clang-6.0+0x1dd43cf)
#10 0x01dd4faa
llvm::DomTreeBuilder::SemiNCAInfo >::DeleteEdge(llvm::DominatorTreeBase&,
llvm::DomTreeBuilder::SemiNCAInfo >::BatchUpdateInfo*, llvm::BasicBlock*, llvm::BasicBlock*) [clone
.constprop.601] (/usr/local/clang-trunk/bin/clang-6.0+0x1dd4faa)
#11 0x0208873d (anonymous
namespace)::AggressiveDeadCodeElimination::removeDeadInstructions()
(/usr/local/clang-trunk/bin/clang-6.0+0x208873d)
#12 0x02089efa (anonymous
namespace)::ADCELegacyPass::runOnFunction(llvm::Function&) [clone .part.391]
(/usr/local/clang-trunk/bin/clang-6.0+0x2089efa)
#13 0x01e229c3 llvm::FPPassManager::runOnFunction(llvm::Function&)
(/usr/local/clang-trunk/bin/clang-6.0+0x1e229c3)
#14 0x018c04f6 (anonymous
namespace)::CGPassManager::runOnModule(llvm::Module&)
(/usr/local/clang-trunk/bin/clang-6.0+0x18c04f6)
#15 0x01e2370a llvm::legacy::
[llvm-bugs] [Bug 34259] New: LLVM intrinsic emitter should split Intrinsics.gen to minimize project rebuilds on Intrinsics*.td file chanes
https://bugs.llvm.org/show_bug.cgi?id=34259 Bug ID: 34259 Summary: LLVM intrinsic emitter should split Intrinsics.gen to minimize project rebuilds on Intrinsics*.td file chanes Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Core LLVM classes Assignee: unassignedb...@nondot.org Reporter: r...@google.com CC: llvm-bugs@lists.llvm.org First, changing intrinsic properties (IntrNoMem, etc) is basically a full-project rebuild. However, those properties aren't used to make the intrinsic enums that most TUs need. Step 1 would be to split Intrinsics.gen into IntrinsicEnums.gen and IntrinsicProperties.gen or something. Step two would be to go further and eliminate the target-specific intrinsic enums from the enum header, similar to how clang implements DiagnosticSemaKinds.h etc, so that only code mucking with x86 intrinsics includes the x86 intrinsic enums. -- 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 34048] Bad line info in PDB generated by LLD
https://bugs.llvm.org/show_bug.cgi?id=34048 Zachary Turner 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 34054] WinDbg claims that our PDB does not have private symbols:
https://bugs.llvm.org/show_bug.cgi?id=34054 Zachary Turner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |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 34049] Cannot view local variables in WinDbg with LLD generated PDB
https://bugs.llvm.org/show_bug.cgi?id=34049 Zachary Turner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |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 34260] New: Output S_OBJNAME and S_COMPILE3 symbols
https://bugs.llvm.org/show_bug.cgi?id=34260 Bug ID: 34260 Summary: Output S_OBJNAME and S_COMPILE3 symbols Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: DebugInfo Assignee: ztur...@google.com Reporter: ztur...@google.com CC: llvm-bugs@lists.llvm.org MSVC outputs an S_OBJNAME and S_COMPILE3 CodeView record into each module's .debug$S section. clang-cl is not outputting these, which could have unknown effects on the linker. We should output these. -- 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 34261] New: Clang does not output local variable information with /O0 /Od for NRVO'ed variables.
https://bugs.llvm.org/show_bug.cgi?id=34261
Bug ID: 34261
Summary: Clang does not output local variable information with
/O0 /Od for NRVO'ed variables.
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: DebugInfo
Assignee: l...@inglorion.net
Reporter: ztur...@google.com
CC: llvm-bugs@lists.llvm.org
std::string func() {
std::string S = "foo";
S += " bar";
return S;
}
if you build with clang-cl at O0 and /Od and set a breakpoint, MSVC and WinDbg
will say that variable information for S is not present.
--
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 34262] New: Output S_FRAMEPROC symbols
https://bugs.llvm.org/show_bug.cgi?id=34262 Bug ID: 34262 Summary: Output S_FRAMEPROC symbols Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: DebugInfo Assignee: unassignedb...@nondot.org Reporter: ztur...@google.com CC: llvm-bugs@lists.llvm.org S_FRAMEPROC will help stack unwinding in certain less common scenarios, we should emit 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 34263] New: Fill out DbgStart and DbgEnd fields of S_*PROC32 symbols
https://bugs.llvm.org/show_bug.cgi?id=34263 Bug ID: 34263 Summary: Fill out DbgStart and DbgEnd fields of S_*PROC32 symbols Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: DebugInfo Assignee: unassignedb...@nondot.org Reporter: ztur...@google.com CC: llvm-bugs@lists.llvm.org These represent the size of the prologue and epilogue of a function. Outputting these helps a debugger to know where to set breakpoints and how to step into, over, and out of a function. We should be setting these. -- 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 34264] New: Please backport linked library fixes needed for lldb on Gentoo
https://bugs.llvm.org/show_bug.cgi?id=34264 Bug ID: 34264 Summary: Please backport linked library fixes needed for lldb on Gentoo Product: new-bugs Version: 5.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mgo...@gentoo.org CC: llvm-bugs@lists.llvm.org Blocks: 33849 The following four commits from master are necessary to fix lldb build on Gentoo which has been broken in 5.0 trunk: r310712 -- [cmake] Expose the dependencies of ExecutionEngine as PUBLIC r311122 -- [cmake] Add explicit linkage from Core to curses r311354 -- [cmake] Explicitly link dependency libraries in the Host library r311355 -- [unittests] Build LLVMTestingSupport for out-of-source builds (the first one applies to LLVM, the remaining to LLDB) Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=33849 [Bug 33849] [meta] 5.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34265] New: DelayedTypos assertion with bad arguments to __builtin_astype()
https://bugs.llvm.org/show_bug.cgi?id=34265
Bug ID: 34265
Summary: DelayedTypos assertion with bad arguments to
__builtin_astype()
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: OpenCL
Assignee: unassignedclangb...@nondot.org
Reporter: chrisc@gmail.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19020
--> https://bugs.llvm.org/attachment.cgi?id=19020&action=edit
Stack trace
The following code causes an assertion `DelayedTypos.empty()` in clang/sema
with message `Uncorrected typos!`:
void A() {
__builtin_astype(x, x);
}
Full stack trace attached. Changing the second argument as such:
void A() {
__builtin_astype(x, int);
}
Causes an unreachable in ASTContext.cpp with message `Unknown builtin type!`.
Using argument -fno-spell-checking prevents both errors.
--
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 33921] ARM NEON vectorization miscompiles code in 5.0
https://bugs.llvm.org/show_bug.cgi?id=33921 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #49 from Hans Wennborg --- (In reply to Renato Golin from comment #48) > Hi Hans, patch looks good for backporting. > > Cheers, > Renato Merged in r311369. Thanks! -- 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
https://bugs.llvm.org/show_bug.cgi?id=33849 Bug 33849 depends on bug 33921, which changed state. Bug 33921 Summary: ARM NEON vectorization miscompiles code in 5.0 https://bugs.llvm.org/show_bug.cgi?id=33921 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 34266] New: [maybe regression]: undefined behavior due to misaligned access to aligned lambda
https://bugs.llvm.org/show_bug.cgi?id=34266
Bug ID: 34266
Summary: [maybe regression]: undefined behavior due to
misaligned access to aligned lambda
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: gonzalob...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
When compiling the following code with: clang++ -fsanitize=undefined -std=c++14
I get the following error:
mwe.cpp:30:14: runtime error: load of misaligned address 0x0042ff61 for
type 'const (lambda at mwe.cpp:30:14) *', which requires 8 byte alignment
0x0042ff61: note: pointer points here
00 00 00 00 00 4b 46 69 76 45 00 50 bc 63 00 00 00 00 00 62 ff 42 00 00 00
00 00 2f 61 69 61 2f
^
initial debugging suggest that the lambda, which is properly aligned in
E::operator() is accessed via a misaligned pointer in D::operator(),
introducing undefined behavior. How this happens escapes me.
The reproducer is:
template
struct static_const { static constexpr T value {}; };
template
constexpr T static_const::value;
struct B {
static constexpr int bar(int) noexcept { return 0; }
constexpr int baz(int) noexcept { return 0; }
};
struct C {
auto operator()() const noexcept -> int { return 0; }
};
namespace {
constexpr auto const& c_fn = static_const::value;
}
struct D {
template
auto operator()(F&& f) const noexcept -> int { return f(0); }
};
namespace { constexpr auto const& d_fn = static_const::value; }
struct E {
template
auto operator()(T t = B()) const noexcept -> T {
auto l = [&](int i) { return t.baz(T::bar(i)); };
d_fn(l);
return t;
}
};
namespace { constexpr auto const& e_fn = static_const::value; }
int main() {
auto a = c_fn();
auto b = e_fn();
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 34264] Please backport linked library fixes needed for lldb on Gentoo
https://bugs.llvm.org/show_bug.cgi?id=34264 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED CC||h...@chromium.org Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- (In reply to Michał Górny from comment #0) > The following four commits from master are necessary to fix lldb build on > Gentoo which has been broken in 5.0 trunk: > > r310712 -- [cmake] Expose the dependencies of ExecutionEngine as PUBLIC r311372. > r311122 -- [cmake] Add explicit linkage from Core to curses > r311354 -- [cmake] Explicitly link dependency libraries in the Host library > r311355 -- [unittests] Build LLVMTestingSupport for out-of-source builds r311376. Since the last ones landed pretty recently, please let me know in case there are any follow-ups that need to be merged also. -- 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
https://bugs.llvm.org/show_bug.cgi?id=33849 Bug 33849 depends on bug 34264, which changed state. Bug 34264 Summary: Please backport linked library fixes needed for lldb on Gentoo https://bugs.llvm.org/show_bug.cgi?id=34264 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 33789] Remove old OptRemark API
https://bugs.llvm.org/show_bug.cgi?id=33789 Sam Elliott changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Sam Elliott --- https://reviews.llvm.org/rL311380 -- 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 32043] LSR takes a long time for the testcase
https://bugs.llvm.org/show_bug.cgi?id=32043 Wei Mi changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #8 from Wei Mi --- It was fixed at rL300494 and then rL300494 was superseded by rL306785. -- 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 34267] New: [ICE][coroutines] Instruction does not dominate all uses
https://bugs.llvm.org/show_bug.cgi?id=34267 Bug ID: 34267 Summary: [ICE][coroutines] Instruction does not dominate all uses Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: enieb...@boost.org CC: llvm-bugs@lists.llvm.org Created attachment 19021 --> https://bugs.llvm.org/attachment.cgi?id=19021&action=edit repro clang++ corobug.cpp -Wall -Wextra -O2 -march=native -std=gnu++2a "-fcoroutines-ts" results in: Instruction does not dominate all uses! %23 = call noalias nonnull i8* @llvm.coro.begin(token %12, i8* %21), !noalias !45 %63 = phi i8* [ %23, %61 ] fatal error: error in backend: Broken function found, compilation aborted! clang-6.0: error: clang frontend command failed with exit code 70 (use -v to see invocation) clang version 6.0.0 (https://github.com/llvm-mirror/clang.git fbdebfae845511dae1ff852aa303205a1dee5ebf) (https://github.com/llvm-mirror/llvm.git 3ef5d9d5ddb0b40bea3f7bcb2163aeff0280acdb) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /opt/wandbox/clang-head/bin (See https://wandbox.org/permlink/Xb9KQ90mgHyovhXF) Compiling without optimization results in no error. -- 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 34268] New: JITting of x32 code on x64 fails with crash or instruction selection error.
https://bugs.llvm.org/show_bug.cgi?id=34268
Bug ID: 34268
Summary: JITting of x32 code on x64 fails with crash or
instruction selection error.
Product: libraries
Version: 4.0
Hardware: Macintosh
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: OrcJIT
Assignee: unassignedb...@nondot.org
Reporter: 1101.deb...@gmail.com
CC: llvm-bugs@lists.llvm.org
I compile a simple code:
// main.c
#include
int square(int x) {
return x * x;
}
int main() {
printf("%d\n", square(4));
return 0;
}
Using the following command:
> clang-4.0 main.c -c -emit-llvm -m32
Then I try to run the bitcode using lli. Based on jit kind it either crashes or
shows an instruction selection error:
> lli-4.0 -jit-kind=orc-mcjit main.bc
0 libLLVM-4.0.so.1 0x7fa69adc49a8
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 56
1 libLLVM-4.0.so.1 0x7fa69adc2b2e llvm::sys::RunSignalHandlers() + 62
2 libLLVM-4.0.so.1 0x7fa69adc2c7c
3 libpthread.so.0 0x7fa69a4aa390
4 libpthread.so.0 0x7fa69d81e026
Stack dump:
0. Program arguments: lli-4.0 -jit-kind=orc-mcjit main.bc
fish: “lli-4.0 -jit-kind=orc-mcjit mai…” terminated by signal SIGSEGV (Address
boundary error)
> lli-4.0 main.bc
0 libLLVM-4.0.so.1 0x7f2377ae19a8
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 56
1 libLLVM-4.0.so.1 0x7f2377adfb2e llvm::sys::RunSignalHandlers() + 62
2 libLLVM-4.0.so.1 0x7f2377adfc7c
3 libpthread.so.0 0x7f23771c7390
4 libpthread.so.0 0x7f237a53b026
Stack dump:
0. Program arguments: lli-4.0 main.bc
fish: “lli-4.0 main.bc” terminated by signal SIGSEGV (Address boundary error)
> lli-4.0 -jit-kind=orc-lazy main.bc
LLVM ERROR: Cannot select: 0x199d480: ch,glue = X86ISD::CALL 0x199d418,
0x199d758, Register:i32 %EDI, Register:i32 %ESI, Register:i8 %AL,
RegisterMask:Untyped, 0x199d418:1
0x199d758: i32 = X86ISD::Wrapper TargetGlobalAddress:i32 0
0x199d140: i32 = TargetGlobalAddress 0
0x199ce00: i32 = Register %EDI
0x199d2e0: i32 = Register %ESI
0x199d3b0: i8 = Register %AL
0x199ced0: Untyped = RegisterMask
0x199d418: ch,glue = CopyToReg 0x199d348, Register:i8 %AL, Constant:i8<0>,
0x199d348:1
0x199d3b0: i8 = Register %AL
0x199d210: i8 = Constant<0>
0x199d348: ch,glue = CopyToReg 0x199d278, Register:i32 %ESI, 0x199d070,
0x199d278:1
0x199d2e0: i32 = Register %ESI
0x199d070: i32,ch,glue = CopyFromReg 0x199cfa0, Register:i32 %EAX,
0x199cfa0:1
0x199d008: i32 = Register %EAX
0x199cfa0: ch,glue = callseq_end 0x199cf38, TargetConstant:i32<0>,
TargetConstant:i32<0>, 0x199cf38:1
0x199cd30: i32 = TargetConstant<0>
0x199cd30: i32 = TargetConstant<0>
0x199cf38: ch,glue = X86ISD::CALL 0x199ce68, 0x199d7c0, Register:i32
%EDI, RegisterMask:Untyped, 0x199ce68:1
0x199d7c0: i32 = X86ISD::Wrapper TargetGlobalAddress:i32 0
0x199d0d8: i32 = TargetGlobalAddress 0
0x199ce00: i32 = Register %EDI
0x199ced0: Untyped = RegisterMask
0x199ce68: ch,glue = CopyToReg 0x199cd98, Register:i32 %EDI,
Constant:i32<4>
0x199ce00: i32 = Register %EDI
0x199ccc8: i32 = Constant<4>
0x199d278: ch,glue = CopyToReg 0x199d1a8, Register:i32 %EDI, 0x199d6f0
0x199ce00: i32 = Register %EDI
0x199d6f0: i32 = X86ISD::Wrapper TargetGlobalAddress:i32<[4 x i8]*
@"$static.0"> 0
0x199d688: i32 = TargetGlobalAddress<[4 x i8]* @"$static.0"> 0
In function: main
===
I tested it only on Linux, but other systems might be affected as well.
--
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 32390] version list clang_rt.asan-dynamic-arm.vers isn't generated
https://bugs.llvm.org/show_bug.cgi?id=32390 Evgeniy Stepanov changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Evgeniy Stepanov --- r311394. Thanks for the patch! -- 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 34269] New: Clang 5.0.0 RC2 doesn't recognize DevDiv internal builds of MSVC
https://bugs.llvm.org/show_bug.cgi?id=34269 Bug ID: 34269 Summary: Clang 5.0.0 RC2 doesn't recognize DevDiv internal builds of MSVC Product: clang Version: 5.0 Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: sfi...@hotmail.com CC: llvm-bugs@lists.llvm.org Mail thread: https://lists.llvm.org/pipermail/cfe-dev/2017-August/055022.html Fixed in master by r311391: https://reviews.llvm.org/D36860 To summarize, there's a regression between Clang 4.0.1 and 5.0.0 RC2, where Clang no longer recognizes the DevDiv-internal directory structure of MSVC builds. This makes it more difficult for us to test MSVC's STL with Clang (such testing helps us avoid writing code that unintentionally depends on non-Standard behavior of C1XX, and also helps us find bugs in Clang). While I figured out a workaround for this regression (explicitly pass -fms-compatibility-version and invoke link.exe separately), it would be great if the fix r311391 could be merged into 5.0.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 21120] -pass-remarks=inline doesn't seem to work on x86_64-unknown-linux-gnu
https://bugs.llvm.org/show_bug.cgi?id=21120 Sam Elliott changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||as...@cs.washington.edu --- Comment #1 from Sam Elliott --- I took a look at this today. I think this is fixed. If I set `target triple` to "x86_64-unknown-linux-gnu" in the file, then the test now passes. -- 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
https://bugs.llvm.org/show_bug.cgi?id=33849 Bug 33849 depends on bug 34181, which changed state. Bug 34181 Summary: Regressions in written import libraries since 4.0 https://bugs.llvm.org/show_bug.cgi?id=34181 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 34181] Regressions in written import libraries since 4.0
https://bugs.llvm.org/show_bug.cgi?id=34181 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Hans Wennborg --- (In reply to Hans Wennborg from comment #3) > (In reply to Martin Storsjö from comment #1) > > These issues have now been fixed on SVN trunk - to fix, please backport SVN > > r310988-r310992 to the 5.0 branch. > > > > 310988 (for llvm) and 310989 (for lld) together fix the first issue > > mentioned. > > 310990 (for llvm) fixes the issue with llvm-dlltool, which isn't a > > regression but still a worthy backport > > 310991 (for llvm) and 310992 (for lld) together fix the second issue > > mentioned > > I've merged all of those except r310990, as someone replied with a concern > about buildbot breakage. I'll merge that one when that's resolved. Merged that one in r311408. -- 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
https://bugs.llvm.org/show_bug.cgi?id=33849 Bug 33849 depends on bug 34177, which changed state. Bug 34177 Summary: AVX512 miscompile during type legalization of v4i1 = setcc v4i64, v4i64 https://bugs.llvm.org/show_bug.cgi?id=34177 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 34177] AVX512 miscompile during type legalization of v4i1 = setcc v4i64, v4i64
https://bugs.llvm.org/show_bug.cgi?id=34177 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Hans Wennborg --- (In reply to Hans Wennborg from comment #6) > (In reply to Elad Cohen from comment #5) > > It passed with 4.0, so I guess we should have it merged to 5.0. > > > > Adding Hans, and marking as a blocker. > > Sounds good to me. Let's have it sit in trunk a little longer, and then I'll > merge. Merged in r311409. -- 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 19668] GCC ABI incompatibility when passing object with trivial copy ctor, trivial dtor, and non-trivial move ctor
https://bugs.llvm.org/show_bug.cgi?id=19668 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Hans Wennborg --- Merged in r311410. -- 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
https://bugs.llvm.org/show_bug.cgi?id=33849 Bug 33849 depends on bug 19668, which changed state. Bug 19668 Summary: GCC ABI incompatibility when passing object with trivial copy ctor, trivial dtor, and non-trivial move ctor https://bugs.llvm.org/show_bug.cgi?id=19668 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 34270] New: Emit S_REGREL32 and S_BPREL32 instead of S_LOCAL / S_DEFRANGE*
https://bugs.llvm.org/show_bug.cgi?id=34270 Bug ID: 34270 Summary: Emit S_REGREL32 and S_BPREL32 instead of S_LOCAL / S_DEFRANGE* Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: DebugInfo Assignee: ztur...@google.com Reporter: ztur...@google.com CC: llvm-bugs@lists.llvm.org These symbols are more compact and only require 1 record per symbol as opposed to 2, so should greatly reduce PDB bloat. -- 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 34271] New: incorrect instruction selected for materializing 4-way add of 0x01010101
https://bugs.llvm.org/show_bug.cgi?id=34271
Bug ID: 34271
Summary: incorrect instruction selected for materializing 4-way
add of 0x01010101
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: richard-l...@metafoo.co.uk
CC: llvm-bugs@lists.llvm.org
We miscompile ffmpeg's mjpegenc_common.c due to a bad instruction being
selected to materialize a vector constant. Testcase:
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define <4 x i32> @f(<4 x i32> %a) {
%v = add nuw nsw <4 x i32> %a,
ret <4 x i32> %v
}
This compiles to:
pcmpeqd %xmm1, %xmm1
psubd %xmm1, %xmm0
... which computes %a + {1, 1, 1, 1}, not %a + {0x01010101, 0x01010101,
0x01010101, 0x01010101}.
--
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 34272] New: abi for passing empty structures on x86 changed between recently
https://bugs.llvm.org/show_bug.cgi?id=34272
Bug ID: 34272
Summary: abi for passing empty structures on x86 changed
between recently
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: var...@gmail.com
CC: llvm-bugs@lists.llvm.org
Take the following test case on osx:
<
#include
typedef struct {
} Empty;
Empty ret_empty (int i) {
Empty e;
printf ("%d\n", i);
return e;
}
In xcode7.3, which has clang version:
Apple LLVM version 7.3.0 (clang-703.0.29)
Running
clang -emit-llvm empty.c
generates the following:
define void @ret_empty(%struct.Empty* noalias sret %agg.result, i32 %i) #0 {
i.e. the struct is returned using a hidden parameter
In xcode8.3 and later, it generates the following:
define void @ret_empty(i32) #0 {
i.e. the return value is simply ignored.
The change seems to have been introduced by:
https://github.com/llvm-mirror/clang/commit/bc350ca21c51e341427c7f96dc21fc1bd8f73a2b
The commit talks about the MCU abi, but the change seems to impact normal
linux/osx etc. as well, which seems to be an abi break. Was this intentional,
or is this a regression ?
For the record, gcc generates the same code as xcode7.3.
--
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 34271] incorrect instruction selected for materializing 4-way add of 0x01010101
https://bugs.llvm.org/show_bug.cgi?id=34271 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Craig Topper --- Fixed in r311429. Both test cases fail on 5.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
