[llvm-bugs] [Bug 26849] New: LibASTMatchersReference still doesnt'work
https://llvm.org/bugs/show_bug.cgi?id=26849 Bug ID: 26849 Summary: LibASTMatchersReference still doesnt'work Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Documentation Assignee: unassignedclangb...@nondot.org Reporter: piotr.padlew...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified http://clang.llvm.org/docs/LibASTMatchersReference.html doesn't work -- 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 26501] error : clang frontend command failed due to signal (use -v to see invocation)
https://llvm.org/bugs/show_bug.cgi?id=26501 reupenl...@forward.cat changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from reupenl...@forward.cat --- Not seeing this in LLVM-3.8.0-rc3-win64.exe. -- 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 26850] New: Lookup of operator[] succeeds when should be ambiguous
https://llvm.org/bugs/show_bug.cgi?id=26850
Bug ID: 26850
Summary: Lookup of operator[] succeeds when should be ambiguous
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: barry.rev...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
Consider the following reduced code example from a StackOverflow question
(http://stackoverflow.com/q/35373384/2069064):
struct X{};
struct Y{};
struct B
{
void operator[](X){}
};
struct C
{
void operator[](Y){}
};
struct D : B, C {};
int main()
{
D d;
d[Y()];
}
The call to D::operator[] should be ambiguous due to the two different base
class overloads. A call to d.operator[](Y()) would correctly fail to compile.
--
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 26851] New: clang-cl doesn't recognize -fuse-ld=lld
https://llvm.org/bugs/show_bug.cgi?id=26851 Bug ID: 26851 Summary: clang-cl doesn't recognize -fuse-ld=lld Product: clang Version: 3.7 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: ignacio.slipk...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified I'm trying to compile and link from Visual Studio 2015 using the LLVM toolchain, however it uses Visual Studio's link.exe I can't seem to be able to force it to use lld.exe/lld-link.exe by passing -fuse-ld=lld to the compiler arguments in "Additional Options" in Visual Studio. clang-cl returns "no such file or directory: -fuse-ld=lld" -- 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 26852] New: false negative for -Wconstant-logical-operand in C++ mode, not in C
https://llvm.org/bugs/show_bug.cgi?id=26852
Bug ID: 26852
Summary: false negative for -Wconstant-logical-operand in C++
mode, not in C
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: ed0.88.p...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
Consider this snippet code:
$ cat enum_constant_operand.cpp
int bar();
typedef enum
{
X = 1,
Y = 2,
Z = 4,
} val_t;
int foo()
{
int val = bar();
return (val == X || Y || Z);
}
EOF
If it's compiled in C mode, it reports:
$ clang++ -x c enum_constant_operand.cpp -fsyntax-only
enum_constant_operand.cpp:13:19: warning: use of logical '||' with constant
operand [-Wconstant-logical-operand]
return (val == X || Y || Z);
^ ~
enum_constant_operand.cpp:13:19: note: use '|' for a bitwise operation
return (val == X || Y || Z);
^~
|
enum_constant_operand.cpp:13:24: warning: use of logical '||' with constant
operand [-Wconstant-logical-operand]
return (val == X || Y || Z);
^ ~
enum_constant_operand.cpp:13:24: note: use '|' for a bitwise operation
return (val == X || Y || Z);
^~
|
2 warnings generated.
$
If it's compiled in C++, it won't report anything:
$ clang++ enum_constant_operand.cpp -fsyntax-only
$
--
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 26853] New: __attribute__(
https://llvm.org/bugs/show_bug.cgi?id=26853 Bug ID: 26853 Summary: __attribute__( Product: clang Version: 3.7 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: simonas+llvm@kazlauskas.me CC: llvm-bugs@lists.llvm.org Classification: Unclassified -- 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 26847] coverage flushing unlocks and closes file in the wrong order
https://llvm.org/bugs/show_bug.cgi?id=26847 Vedant Kumar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Vedant Kumar --- Fixed in compiler-rt r262779. Looks like this (on Darwin) now: 16770/0x69122:285755 9 4 flock(0x3, 0x8, 0x10)= 0 0 16770/0x69122:2877732010 2004 close_nocancel(0x3) = 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 26854] New: clang++ crashes on valid code on x86_64-linux-gnu with no diagnostic msg
https://llvm.org/bugs/show_bug.cgi?id=26854
Bug ID: 26854
Summary: clang++ crashes on valid code on x86_64-linux-gnu with
no diagnostic msg
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: helloqi...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
The current clang++ trunk crashes when compiling the following (syntactically)
valid code on x86_64-linux-gnu in both 32-bit and 64-bit modes.
It crashes clang++ versions later than 2.9.
$ clang++-trunk -v
clang version 3.9.0 (trunk 262770) (llvm/trunk 262769)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/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.3
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/3.4.6
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.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.3.0
Found candidate GCC installation:
/usr/local/bin/../lib/gcc/x86_64-unknown-linux-gnu/5.3.0
Selected GCC installation:
/usr/local/bin/../lib/gcc/x86_64-unknown-linux-gnu/5.3.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64
$ clang++-trunk abc.cc
clang-3.9: error: unable to execute command: Segmentation fault (core dumped)
clang-3.9: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 3.9.0 (trunk 262770) (llvm/trunk 262769)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin
clang-3.9: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang-3.9: note: diagnostic msg:
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-3.9: note: diagnostic msg: /tmp/abc-272dce.cpp
clang-3.9: note: diagnostic msg: /tmp/abc-272dce.sh
clang-3.9: note: diagnostic msg:
$ cat abc.cc
struct A
{
A (...);
};
int main ()
{
volatile A a;
A a2 (a);
}
--
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 26839] Clang -cc1 crashes if an unknown -target-cpu is passed for -triple arm
https://llvm.org/bugs/show_bug.cgi?id=26839 Saleem Abdulrasool changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Saleem Abdulrasool --- SVN r262778, SVN r262790. -- 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
