[llvm-bugs] [Bug 50240] New: Missing APPEND in ACCESS specifier of OPEN statement

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50240

Bug ID: 50240
   Summary: Missing APPEND in ACCESS specifier of OPEN statement
   Product: flang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Frontend
  Assignee: unassignedb...@nondot.org
  Reporter: orop...@gmail.com
CC: david.tr...@arm.com, jper...@nvidia.com,
kirankuma...@gmail.com, llvm-bugs@lists.llvm.org,
sscalp...@nvidia.com

Here's the minimal reproducer

program main
lu = 60
open(lu,file='dcp.out',status='old',access='append',err=10)
10  continue
end program main


flang-new -fc1 main.f90

./main.f90:3:48: error: Invalid ACCESS value 'append'
  open(lu,file='dcp.out',status='old',access='append',err=10)
 
error: Semantic errors in main.f90

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

[llvm-bugs] [Bug 50241] New: `signal` returns wrong pointer with `-fsanitize=memory`

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50241

Bug ID: 50241
   Summary: `signal` returns wrong pointer with
`-fsanitize=memory`
   Product: clang
   Version: 11.0
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: enzo.baldisse...@outlook.fr
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

Created attachment 24833
  --> https://bugs.llvm.org/attachment.cgi?id=24833&action=edit
Valgrind usage on produced `signal` executable

The code below produces unexpected result with `fsanitize=memory`.
This was tested on WSL 2 (uname -a : `Linux DESKTOP-I5KOTDQ
4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux`) and Arch Linux (a colleague did the test, I don't have much
more information about his system, sorry), using both clang-10 and clang-11.

```c
// signal.c
#include 
#include 
#include 

void handler1(int signal) {
puts("handler1 called");
exit(0);
}

void handler2(int signal) {
puts("handler2 called");
exit(0);
}

int main(void) {
// ignore the return value, it doesn't matter here
signal(SIGUSR1, handler1);
// `signal` returns the former handler
// so here, it should be `handler1`
__sighandler_t should_be_handler1 = signal(SIGUSR1, handler2);
// and here, "handler1 called" should be printed
should_be_handler1(SIGUSR1);
return 0;
}
```

```sh
$ clang -o signal signal.c
$ ./signal
handler1 called
$ clang -o signal -fsanitize=memory signal.c
$ ./signal
handler2 called
```

When using valgrind on the produced `signal` executable, my PC's resources
consumption peeked (see attachment), and my colleague's computer froze.

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

[llvm-bugs] [Bug 50242] New: Cherry-pick 6329ce75da7a44c40d4406bf48ffffe973ef5fdb

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50242

Bug ID: 50242
   Summary: Cherry-pick 6329ce75da7a44c40d4406bf48e973ef5fdb
   Product: clang-tools-extra
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: clangd
  Assignee: unassignedclangb...@nondot.org
  Reporter: kadircetinkaya.06...@gmail.com
CC: llvm-bugs@lists.llvm.org

This is a privacy fix we missed in 12 release and would like to get it into
point releases.

It was causing a merge conflict, for resolution you can check
https://github.com/kadircet/llvm-project/commit/4abdc8352d0852e8d527aa25c87597ad060f001d.
Basically ignore the `llvm::reverse` in the for body.

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

[llvm-bugs] [Bug 50243] New: [clang-format] Misformatted initializion list with preprocessor directives

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50243

Bug ID: 50243
   Summary: [clang-format] Misformatted initializion list with
preprocessor directives
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: curde...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org

That's somehow related to https://llvm.org/PR31427.

It seems that in the presence of preprocessor directives, the braces in the
ctor's initialization list are considered to be braces that start the function
body scope.

With default LLVM style:
```
class Sok
{
Sok()
: i{0}
{}
};

// actual:
class Sbad
{
Sbad()
#ifdef X
: i
{
0
}
#else
: i
{
1
}
#endif
{}
};

/* expected:
class Sbad
{
Sbad()
#ifdef X
: i{0}
#else
: i{1}
#endif
{}
};
*/
```

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

[llvm-bugs] Issue 34020 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-gisel: ASSERT: SrcTy.getNumElements() == DstTy.getNumElements() && "different number of element

2021-05-06 Thread ClusterFuzz-External via monorail via llvm-bugs 
Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, 
d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, 
llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, 
mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible 
Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-05-06
Type: Bug

New issue 34020 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-gisel: 
ASSERT: SrcTy.getNumElements() == DstTy.getNumElements() && "different number 
of element
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34020

Detailed Report: https://oss-fuzz.com/testcase?key=4835611786739712

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-isel-fuzzer--aarch64-gisel
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  SrcTy.getNumElements() == DstTy.getNumElements() && "different number of 
element
  llvm::MachineIRBuilder::validateTruncExt
  llvm::MachineIRBuilder::buildInstr
  
Sanitizer: address (ASAN)

Regressed: 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202105050630:202105060608

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4835611786739712

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for 
instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any 
stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other 
feedback, please file an issue at https://github.com/google/oss-fuzz/issues. 
Comments on individual Monorail issues are not monitored.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 50244] New: compiler-rt build failing on 32-bit x86 Linux platform: bits/c++config.h not found

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50244

Bug ID: 50244
   Summary: compiler-rt build failing on 32-bit x86 Linux
platform: bits/c++config.h not found
   Product: new-bugs
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: lukebe...@hotmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org

The fix for Bug 49827, https://github.com/llvm/llvm-project/commit/e92d2b80c6c9

Is causing Debian 10 i386, OpenSUSE Tumbleweed i686, and Arch Linux 32,
compiler-rt release builds to fail with

[ 96%] Generating SANITIZER_TEST_OBJECTS.sanitizer_allocator_test.cpp.i386.o
..In file included from
/compiler-rt/lib/sanitizer_common/tests/sanitizer_allocator_test.cpp:17:
In file included from
/compiler-rt/lib/sanitizer_common/tests/sanitizer_test_utils.h:27:
In file included from
/compiler-rt/lib/sanitizer_common/tests/sanitizer_test_config.h:19:
In file included from
/usr/lib/gcc/i586-suse-linux/10/../../../../include/c++/10/vector:60:
/usr/lib/gcc/i586-suse-linux/10/../../../../include/c++/10/bits/stl_algobase.h:59:10:
fatal error: 'bits/c++config.h' file not found
#include 
 ^~
..[ 96%] Generating
INTERCEPTION_TEST_OBJECTS.interception_linux_test.cpp.i386.o
.In file included from
/compiler-rt/lib/interception/tests/interception_linux_test.cpp:19:
In file included from
/home/luke/e64/lo/llvm-project/llvm/utils/unittest/googletest/include/gtest/gtest.h:54:
/usr/lib/gcc/i586-suse-linux/10/../../../../include/c++/10/limits:42:10: fatal
error: 'bits/c++config.h' file not found
#include 
 ^~
...1 error generated.
.make[3]: ***
[projects/compiler-rt/lib/interception/tests/CMakeFiles/TInterception-i386-Test.dir/build.make:91:
projects/compiler-rt/lib/interception/tests/INTERCEPTION_TEST_OBJECTS.interception_linux_test.cpp.i386.o]
Error 1
make[2]: *** [CMakeFiles/Makefile2:37022:
projects/compiler-rt/lib/interception/tests/CMakeFiles/TInterception-i386-Test.dir/all]
Error 2
make[2]: *** Waiting for unfinished jobs
.[ 96%] Generating SANITIZER_TEST_OBJECTS.sanitizer_atomic_test.cpp.i386.o

--
Ran 126 tests in 0.914s

OK
In file included from
/compiler-rt/lib/sanitizer_common/tests/sanitizer_atomic_test.cpp:13:
In file included from
/home/luke/e64/lo/llvm-project/llvm/utils/unittest/googletest/include/gtest/gtest.h:54:
/usr/lib/gcc/i586-suse-linux/10/../../../../include/c++/10/limits:42:10: fatal
error: 'bits/c++config.h' file not found
#include 
 ^~
1 error generated.
make[3]: ***
[projects/compiler-rt/lib/sanitizer_common/tests/CMakeFiles/TSanitizer-i386-Test.dir/build.make:221:
projects/compiler-rt/lib/sanitizer_common/tests/SANITIZER_TEST_OBJECTS.sanitizer_allocator_test.cpp.i386.o]
Error 1
make[3]: *** Waiting for unfinished jobs
[ 96%] Built target check-clang-python
1 error generated.
make[3]: ***
[projects/compiler-rt/lib/sanitizer_common/tests/CMakeFiles/TSanitizer-i386-Test.dir/build.make:329:
projects/compiler-rt/lib/sanitizer_common/tests/SANITIZER_TEST_OBJECTS.sanitizer_atomic_test.cpp.i386.o]
Error 1
make[2]: *** [CMakeFiles/Makefile2:36497:
projects/compiler-rt/lib/sanitizer_common/tests/CMakeFiles/TSanitizer-i386-Test.dir/all]
Error 2
[ 97%] Built target ToolingTests
make[1]: *** [CMakeFiles/Makefile2:14979: CMakeFiles/check-all.dir/rule] Error
2
make: *** [Makefile:244: check-all] Error 2

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

[llvm-bugs] [Bug 40305] Error on variadic template argument deduction including conversion to reference to const to Base

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=40305

Peter Georg  changed:

   What|Removed |Added

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

--- Comment #3 from Peter Georg  ---
Bug has already been fixed in clang 10.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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 47611] [Windows][AArch64] Inconsistent handling of HFAs/HVAs

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=47611

Richard Townsend  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Richard Townsend  ---
This one was resolved by the above commit.

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

[llvm-bugs] [Bug 50245] New: use of template template parameter 'T' requires template arguments

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50245

Bug ID: 50245
   Summary: use of template template parameter 'T' requires
template arguments
   Product: new-bugs
   Version: 12.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: spot...@amazon.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org

Created attachment 24834
  --> https://bugs.llvm.org/attachment.cgi?id=24834&action=edit
test case code

Starting with clang 12.0.0 (Fedora 34), some C++ code no longer compiles,
throwing the error message in the Summary of this ticket.

I boiled the code down to a test.cpp which exhibits the issue (could probably
boil it down further, but I hope this is good enough). When I put it through
godbolt.org (godbolt.org/z/ToceWcEG7) it compiles in GCC and clang older than
12.0.0, but exhibits the same failure in trunk.

Please let me know what else you need to know to help address this, and thanks
in advance.

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

[llvm-bugs] [Bug 50079] Regression(fc5d804ddbe): lld/mach-o can't link simple binary

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50079

Jez Ng  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #14 from Jez Ng  ---


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

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

[llvm-bugs] [Bug 49597] Support object files / dylibs built for multiple platforms

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49597

Jez Ng  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
 Fixed By Commit(s)||9260760235261a5cd150b15a349
   ||9f7988da65a02

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

[llvm-bugs] [Bug 50246] New: ICE explicit calling a caputered lambda expression with a paramater pack

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50246

Bug ID: 50246
   Summary: ICE explicit calling a caputered lambda expression
with a paramater pack
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: peter.ge...@physik.uni-regensburg.de
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

Created attachment 24835
  --> https://bugs.llvm.org/attachment.cgi?id=24835&action=edit
Crash backtrace

See reduced test-case on Compiler Explorer: https://godbolt.org/z/G4qT3sEf9

According to Compiler Explorer all clang versions (supporting the required
C++11/14 features) are affected by this bug.

clang frontend crashes when explicitly calling a captured lambda expression's
operator() using a parameter pack as arguments. The issue has been observed in
a larger code base in a more complex scenario using the familiar template
syntax for generic lambdas introduced in C++20.

Luckily I've been able to reduce the code to just a few meaning-less lines of
code still showing the same compiler error. While I have been able to rewrite
it using only C++11, the attached reduced code is written using C++14 features.
It just seems easier to understand and removes probably unrelated code.

Code to reproduce:

int main() {
  {
auto const f = [](auto...) {};
[f](auto const... ops) { f.operator()(ops...); }();
  }
}

My tests have shown that in line 4 of the code to reproduce the bug will only
show if all following three conditions are met:
1. The lambda expression f is captured. I.e. not defined within the other
unnamed lambda expression.
2. The lambda expression f is called via explicitly specifying .operator()
3. A parameter pack expansion is used as the arguments for calling the lambda
expression f. The size of the parameter pack does not matter, may be empty.

Attachements:
Crash backtrace, preprocessed source(s), and run script produced on local
machine with clang 11.

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

[llvm-bugs] [Bug 50247] New: [SIMD] calling math builtins (sqrt, ceil, floor, trunc, round) in loop not vectorized

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50247

Bug ID: 50247
   Summary: [SIMD] calling math builtins (sqrt, ceil, floor,
trunc, round) in loop not vectorized
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: WebAssembly
  Assignee: unassignedb...@nondot.org
  Reporter: cl...@evan.coeusgroup.com
CC: llvm-bugs@lists.llvm.org

WASM SIMD128 includes several vector math functions which correspond to scalar
builtins in clang, but calling them for each element in a loop doesn't result
in the appropriate vector instruction.

Here is an example (also at https://godbolt.org/z/v95YvPTGe):


#include 

__f32x4
f32x4_sqrt(__f32x4 a) {
#if USE_BUILTIN
  return __builtin_wasm_sqrt_f32x4(a);
#else
  __f32x4 r;

  for (int i = 0 ; i < 4 ; i++) {
r[i] = __builtin_sqrtf(a[i]);
  }

  return r;
#endif
}

__f64x2
f64x2_sqrt(__f64x2 a) {
#if USE_BUILTIN
  return __builtin_wasm_sqrt_f64x2(a);
#else
  __f64x2 r;

  for (int i = 0 ; i < 2 ; i++) {
r[i] = __builtin_sqrt(a[i]);
  }

  return r;
#endif
}

__f32x4
f32x4_ceil(__f32x4 a) {
#if USE_BUILTIN
  return __builtin_wasm_ceil_f32x4(a);
#else
  __f32x4 r;

  for (int i = 0 ; i < 4 ; i++) {
r[i] = __builtin_ceilf(a[i]);
  }

  return r;
#endif
}

__f64x2
f64x2_ceil(__f64x2 a) {
#if USE_BUILTIN
  return __builtin_wasm_ceil_f64x2(a);
#else
  __f64x2 r;

  for (int i = 0 ; i < 2 ; i++) {
r[i] = __builtin_ceil(a[i]);
  }

  return r;
#endif
}

__f32x4
f32x4_floor(__f32x4 a) {
#if USE_BUILTIN
  return __builtin_wasm_floor_f32x4(a);
#else
  __f32x4 r;

  for (int i = 0 ; i < 4 ; i++) {
r[i] = __builtin_floorf(a[i]);
  }

  return r;
#endif
}

__f64x2
f64x2_floor(__f64x2 a) {
#if USE_BUILTIN
  return __builtin_wasm_floor_f64x2(a);
#else
  __f64x2 r;

  for (int i = 0 ; i < 2 ; i++) {
r[i] = __builtin_floor(a[i]);
  }

  return r;
#endif
}

__f32x4
f32x4_trunc(__f32x4 a) {
#if USE_BUILTIN
  return __builtin_wasm_trunc_f32x4(a);
#else
  __f32x4 r;

  for (int i = 0 ; i < 4 ; i++) {
r[i] = __builtin_truncf(a[i]);
  }

  return r;
#endif
}

__f64x2
f64x2_trunc(__f64x2 a) {
#if USE_BUILTIN
  return __builtin_wasm_trunc_f64x2(a);
#else
  __f64x2 r;

  for (int i = 0 ; i < 2 ; i++) {
r[i] = __builtin_trunc(a[i]);
  }

  return r;
#endif
}

__f32x4
f32x4_nearest(__f32x4 a) {
#if USE_BUILTIN
  return __builtin_wasm_nearest_f32x4(a);
#else
  __f32x4 r;

  for (int i = 0 ; i < 4 ; i++) {
r[i] = __builtin_roundf(a[i]);
  }

  return r;
#endif
}

__f64x2
f64x2_nearest(__f64x2 a) {
#if USE_BUILTIN
  return __builtin_wasm_nearest_f64x2(a);
#else
  __f64x2 r;

  for (int i = 0 ; i < 2 ; i++) {
r[i] = __builtin_round(a[i]);
  }

  return r;
#endif
}

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

[llvm-bugs] [Bug 50248] New: -Wreserved-identifier should not warn on system macros

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50248

Bug ID: 50248
   Summary: -Wreserved-identifier should not warn on system macros
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: lebedev...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

It currently broke google benchmark/test, even when their headers are pulled in
via -isystem.

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

[llvm-bugs] [Bug 50249] New: [Python] CompilationDatabase.getCompileCommands does not work as documented

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50249

Bug ID: 50249
   Summary: [Python] CompilationDatabase.getCompileCommands does
not work as documented
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Tooling
  Assignee: unassignedclangb...@nondot.org
  Reporter: edas...@att.net
CC: llvm-bugs@lists.llvm.org

Created attachment 24838
  --> https://bugs.llvm.org/attachment.cgi?id=24838&action=edit
Standalone reproduction

The documentation for getCompileCommands() says:

Get an iterable object providing all the CompileCommands available to
build filename. Returns None if filename is not found in the database.

The actual behavior for the "not found" case differs in surprising ways:

1. When a regular source file (e.g. .cpp) is not found, an empty iterable is
returned instead of None
2. If a header file (e.g. .h) is not found, a guess at the compile command is
made and returned

I believe the documentation should be updated to reflect the actual behavior.

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

[llvm-bugs] [Bug 45339] Support for bitfields in OpenCL

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=45339

David Rohr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 50251] New: [OpenMP] Custom reduction fails at runtime with misaligned address on NVIDIA V100.

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50251

Bug ID: 50251
   Summary: [OpenMP] Custom reduction fails at runtime with
misaligned address on NVIDIA V100.
   Product: clang
   Version: trunk
  Hardware: Other
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: rgaya...@lbl.gov
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk

Created attachment 24839
  --> https://bugs.llvm.org/attachment.cgi?id=24839&action=edit
A short cpp file  that contains the reproducer.

The test passes if the total size aligns with a power of 2. The reproducer
contains a macro FOUR_D which when turned on the reproducer executes correctly.

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

[llvm-bugs] [Bug 49391] BPF: backport commit 283db5f0837d55f91242812003adf6e189ba743e (fix enum value 0 issue for __builtin_preserve_enum_value())

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49391

Tom Stellard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
 Fixed By Commit(s)|283db5f0837d55f91242812003a |283db5f0837d55f91242812003a
   |df6e189ba743e   |df6e189ba743e e294ece42d85

--- Comment #3 from Tom Stellard  ---
Merged: e294ece42d85

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

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49391, which changed state.

Bug 49391 Summary: BPF: backport commit 
283db5f0837d55f91242812003adf6e189ba743e (fix enum value 0 issue for 
__builtin_preserve_enum_value())
https://bugs.llvm.org/show_bug.cgi?id=49391

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 49455] BPF: backport commit 9c0274cdeae904089806be6faee72b9126d2cf5b

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49455

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|9c0274cdeae904089806be6faee |9c0274cdeae904089806be6faee
   |72b9126d2cf5b   |72b9126d2cf5b a5a6cfe2f030
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Tom Stellard  ---
Merged: a5a6cfe2f030

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

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49455, which changed state.

Bug 49455 Summary: BPF: backport commit 9c0274cdeae904089806be6faee72b9126d2cf5b
https://bugs.llvm.org/show_bug.cgi?id=49455

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49605, which changed state.

Bug 49605 Summary: Merge fcfd3fda71905d7c48f75a531c2265ad3b9876ea into 
release/12.x
https://bugs.llvm.org/show_bug.cgi?id=49605

   What|Removed |Added

 Status|CONFIRMED   |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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 49605] Merge fcfd3fda71905d7c48f75a531c2265ad3b9876ea into release/12.x

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49605

Tom Stellard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Fixed By Commit(s)|fcfd3fda71905d7c48f75a531c2 |fcfd3fda71905d7c48f75a531c2
   |265ad3b9876ea   |265ad3b9876ea e0fe1c58acfa
 Resolution|--- |FIXED

--- Comment #2 from Tom Stellard  ---
Merged: e0fe1c58acfa

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

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 49623, which changed state.

Bug 49623 Summary: [RISCV] Wrong operand order in ISEL pattern for masked 
vmslt[u]
https://bugs.llvm.org/show_bug.cgi?id=49623

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 49623] [RISCV] Wrong operand order in ISEL pattern for masked vmslt[u]

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49623

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|fca5d63aa8d43a21557874d9bc0 |fca5d63aa8d43a21557874d9bc0
   |40e944ab0500d   |40e944ab0500d c1831fc65597
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Tom Stellard  ---
Merged: c1831fc65597

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

[llvm-bugs] [Bug 50161] Stack protector + coroutines + c++ exceptions causing `musttail call must precede a ret with an optional bitcast`

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50161

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|5e3d9fcc3a8802cea5b850a3ca4 |5e3d9fcc3a8802cea5b850a3ca4
   |0c515d916bf82   |0c515d916bf82 471a386a3d34
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #4 from Tom Stellard  ---
Merged: 471a386a3d34

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

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 50161, which changed state.

Bug 50161 Summary: Stack protector + coroutines + c++ exceptions causing 
`musttail call must precede a ret with an optional bitcast`
https://bugs.llvm.org/show_bug.cgi?id=50161

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 50233] Merge 3a62d4fde88544125ce9ceff990db108ee91148a into 12.0.1

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50233

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Fixed By Commit(s)|3a62d4fde88544125ce9ceff990 |3a62d4fde88544125ce9ceff990
   |db108ee91148a   |db108ee91148a 6baa5ce2e4b7
 Status|NEW |RESOLVED

--- Comment #1 from Tom Stellard  ---
Merged: 6baa5ce2e4b7

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

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 50233, which changed state.

Bug 50233 Summary: Merge 3a62d4fde88544125ce9ceff990db108ee91148a into 12.0.1
https://bugs.llvm.org/show_bug.cgi?id=50233

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 50093] Backport `[LoopReroll] Fix rerolling loop with extra instructions` to 12.0.1

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=50093

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|d9a9c992d190dd6645ea911b66c |d9a9c992d190dd6645ea911b66c
   |f0cadba0dadc3   |f0cadba0dadc3 ac593de16cc5
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Tom Stellard  ---
Merged: ac593de16cc5

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

[llvm-bugs] [Bug 49317] [meta] 12.0.1 Release Blockers

2021-05-06 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=49317
Bug 49317 depends on bug 50093, which changed state.

Bug 50093 Summary: Backport `[LoopReroll] Fix rerolling loop with extra 
instructions` to 12.0.1
https://bugs.llvm.org/show_bug.cgi?id=50093

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] Issue 34035 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead

2021-05-06 Thread ClusterFuzz-External via monorail via llvm-bugs 
Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, 
d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, 
llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, 
mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible 
Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-05-07
Type: Bug

New issue 34035 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in 
clang::Preprocessor::PeekAhead
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34035

Detailed Report: https://oss-fuzz.com/testcase?key=4517765131141120

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffcad604dc8
Crash State:
  clang::Preprocessor::PeekAhead
  clang::Parser::isCXX11AttributeSpecifier
  clang::Parser::ParseDeclarationSpecifiers
  
Sanitizer: address (ASAN)

Regressed: 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202105040631:202105050630

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4517765131141120

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for 
instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any 
stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other 
feedback, please file an issue at https://github.com/google/oss-fuzz/issues. 
Comments on individual Monorail issues are not monitored.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs