[llvm-bugs] [Bug 27644] [MIPS] LA macro expansion limitation for PIC mode

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=27644

Milko Leporis  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Milko Leporis  ---
Workaround for this issue was submitted to Chromium source in:
https://codereview.chromium.org/1908253003

-- 
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 39339] New: [DebugInfo@O2][Dexter] Misleading value for local variable at the return statement.

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39339

Bug ID: 39339
   Summary: [DebugInfo@O2][Dexter] Misleading value for local
variable at the return statement.
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: international.phan...@gmail.com
CC: llvm-bugs@lists.llvm.org

Spawned from bug 39187:

By modifying the original test case to:

8<
int main() {
  volatile int foo = 4;

  int beards = 0;
  int birds = 0;

  if (foo == 4) {
beards = 8;
birds = 3;
  } else {
beards = 4;
birds = 6;
  }

  return beards;
}
>8

When stopping at the return, the variable 'birds' shows always the value of
zero.

-- 
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 16145] Missing -mno-tls-direct-seg-refs

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=16145

Ruslan Nikolaev  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 39340] New: Remove "Libraries/Backend: Microblaze" bugzilla component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39340

Bug ID: 39340
   Summary: Remove "Libraries/Backend: Microblaze" bugzilla
component
   Product: Bugzilla Admin
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Products
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: kristof.be...@arm.com, kristof.be...@gmail.com,
llvm-bugs@lists.llvm.org

The component is empty and the backend unsupported

-- 
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 39338] AVX512: Provide support for variable-size mask intrinsics

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39338

Wenzel Jakob  changed:

   What|Removed |Added

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

--- Comment #2 from Wenzel Jakob  ---
Fantastic, I'm closing the ticket in this case.

-- 
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 16692] Microblaze backend faults when using inline assembler with constraints

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=16692

Simon Pilgrim  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED
 CC||llvm-...@redking.me.uk

--- Comment #1 from Simon Pilgrim  ---
The MBlaze backend is no longer supported

-- 
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 39341] New: Remove "Libraries/Backend: Blackfin" bugzilla component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39341

Bug ID: 39341
   Summary: Remove "Libraries/Backend: Blackfin" bugzilla
component
   Product: Bugzilla Admin
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Products
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: kristof.be...@arm.com, kristof.be...@gmail.com,
llvm-bugs@lists.llvm.org

The component is empty and the backend unsupported

-- 
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 39342] New: Add BPF backend component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39342

Bug ID: 39342
   Summary: Add BPF backend component
   Product: Bugzilla Admin
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Products
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: alexei.starovoi...@gmail.com, kristof.be...@arm.com,
kristof.be...@gmail.com, llvm-bugs@lists.llvm.org

We're missing a component for the BPF backend

The default CC should probably be Alexei Starovoitov

-- 
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 39343] New: Remove "Libraries/Backend: Alpha" bugzilla component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39343

Bug ID: 39343
   Summary: Remove "Libraries/Backend: Alpha" bugzilla component
   Product: Bugzilla Admin
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Products
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: kristof.be...@arm.com, kristof.be...@gmail.com,
llvm-bugs@lists.llvm.org,
paul_robin...@playstation.sony.com

The component is empty and the backend unsupported

-- 
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] Issue 9605 in oss-fuzz: llvm/clang-fuzzer: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!"

2018-10-18 Thread sheriff… via monorail via llvm-bugs

Updates:
Labels: Deadline-Approaching

Comment #2 on issue 9605 by sheriff...@chromium.org: llvm/clang-fuzzer:  
ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9605#c2

This bug is approaching its deadline for being fixed, and will be  
automatically derestricted within 7 days. If a fix is planned within 2  
weeks after the deadline has passed, a grace extension can be granted.


- Your friendly Sheriffbot

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


[llvm-bugs] [Bug 39266] typedef types not allowed in vector declaration context

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39266

Jinsong Ji  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #6 from Jinsong Ji  ---
Thanks all! So close this since AltiVec specification says this is ill-formed.

-- 
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 39307] LLVM master breaks Clazy master build

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39307

Stephen Kelly  changed:

   What|Removed |Added

 CC||steve...@gmail.com
 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #1 from Stephen Kelly  ---
Use git if you like:


https://github.com/llvm-mirror/clang/commit/efe41bf98e6011bb413a5056f0025a4509de860d

The 'using llvm::StringRef;' was removed from clang headers.

Clazy needs to be updated to use that itself.

-- 
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 39344] New: uniform_real_distribution can't generate the full range of finite floating point numbers

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39344

Bug ID: 39344
   Summary: uniform_real_distribution can't generate the full
range of finite floating point numbers
   Product: libc++
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: fergus.hender...@gmail.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com

Created attachment 21015
  --> https://bugs.llvm.org/attachment.cgi?id=21015&action=edit
Example program demonstrating the problem.

std::uniform_real_distribution doesn't work if you try to use it to cover the
whole range of available finite floating point numbers:

...
double low = std::numeric_limits::lowest();
double high = std::numeric_limits::max();
std::uniform_real_distribution<> distribution(low, high);
... distribution(generator) ...

In that case, rather than returning a random finite float, it always returns
"inf".

The libc++ code for this function computes (high - low) which in this case ends
up being
   std::numeric_limits::max() - std::numeric_limits::lowest()
and that expression overflows to "inf", which then ends up propagating to the
return value from std::uniform_real_distribution<>::operator().

See the attached example program uniform_real.cc for a test case.

Expected behaviour: program runs successfully with no output.
Observed behaviour: program fails with an assertion failure.

The specific code in the libc++ implementation that is at fault is this
function definition:

template
template
inline
typename uniform_real_distribution<_RealType>::result_type
uniform_real_distribution<_RealType>::operator()(_URNG& __g, const param_type&
__p)
{
return (__p.b() - __p.a())
* _VSTD::generate_canonical<_RealType,
numeric_limits<_RealType>::digits>(__g)
+ __p.a();
}

Note: a similar bug is also present in libstdc++ -- see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87527

-- 
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 39345] New: Conflicting definition/declaration errors from unused submodules

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39345

Bug ID: 39345
   Summary: Conflicting definition/declaration errors from unused
submodules
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Modules
  Assignee: unassignedclangb...@nondot.org
  Reporter: andrew...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

When importing a submodule, an unused/unimported sibling submodule defined in
the same top-level module can cause conflicts in the current compilation unit
if the compilation unit and the unused submodule having conflicting struct
definitions.

Repro at: https://reviews.llvm.org/differential/diff/170103/.

-- 
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 39344] uniform_real_distribution can't generate the full range of finite floating point numbers

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39344

Tim Northover  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||t.p.northo...@gmail.com
 Status|NEW |RESOLVED

--- Comment #1 from Tim Northover  ---
The C++ standard requires the range to be smaller than the largest
representable value so that low & high pair is invalid. From
[rand.dist.uni.real]p2:

"Requires: a ≤ b and b − a ≤ numeric_limits::max()."

-- 
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 39340] Remove "Libraries/Backend: Microblaze" bugzilla component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39340

Tim Northover  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||t.p.northo...@gmail.com
 Status|NEW |RESOLVED

--- Comment #1 from Tim Northover  ---
No bugs in the component so I just nuked it.

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


[llvm-bugs] [Bug 39341] Remove "Libraries/Backend: Blackfin" bugzilla component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39341

Tim Northover  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
 CC||t.p.northo...@gmail.com

--- Comment #1 from Tim Northover  ---
There actually was a bug in there (https://bugs.llvm.org/show_bug.cgi?id=6434)
but it doesn't show up in searches for some reason.

I've disabled the component so it can't be used for any new bugs, which is
probably the best thing we can do.

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


[llvm-bugs] [Bug 39342] Add BPF backend component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39342

Tim Northover  changed:

   What|Removed |Added

 CC||t.p.northo...@gmail.com
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Tim Northover  ---
Done.

-- 
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 39343] Remove "Libraries/Backend: Alpha" bugzilla component

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39343

Tim Northover  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED
 CC||t.p.northo...@gmail.com

--- Comment #1 from Tim Northover  ---
There actually are some bugs in this one:
https://bugs.llvm.org/buglist.cgi?component=Backend%3A%20Alpha&list_id=147907&product=libraries

It's already disabled, so I don't think we should do anything here.

-- 
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 27439] No warning for integer overflow in array size

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=27439

David Bolvansky  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)||344759

--- Comment #2 from David Bolvansky  ---
Fixed in r344759.

-- 
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 39346] New: cplusplus.NewDeleteLeaks would benefit from type information in the message

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39346

Bug ID: 39346
   Summary: cplusplus.NewDeleteLeaks would benefit from type
information in the message
   Product: clang
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Static Analyzer
  Assignee: dcough...@apple.com
  Reporter: ale...@google.com
CC: llvm-bugs@lists.llvm.org

Currently the message generated by the cplusplus.NewDeleteLeaks analyzer
doesn't contain any information about the type of the object potentially being
leaked. In some cases that's not enough (template factory functions and other
cases where the path is not enough to figure out the type).

-- 
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 39347] New: rodata size bloat with file names when using -fsanitize=function with -fsanitize=address

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39347

Bug ID: 39347
   Summary: rodata size bloat with file names when using
-fsanitize=function with -fsanitize=address
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: LLVM Codegen
  Assignee: unassignedclangb...@nondot.org
  Reporter: su...@fb.com
CC: llvm-bugs@lists.llvm.org

I noticed a significant bloat of .rodata section when using both
-fsanitize=function and -fsanitize=address. Inspecting the section showed that
it's significant part are strings with file names. 

I tried to use `-fsanitize-undefined-strip-path-components=-1`, but it happens
to not work with this ubsan check, and the full string names still make it into
the binary.

The repro:
```
# verify file name is not in the rodata 
% cat main.cpp
int main() {return 0;}
% clang++ -fsanitize=function $(realpath main.cpp)
% readelf -p .rodata a.out | grep main.cpp
[Exit 1] # no match

# now enable ASAN
% clang++ -fsanitize=function -fsanitize=address $(realpath main.cpp)
% readelf -p .rodata a.out | grep main.cpp
[ 17680]  /very/long/path/main.cpp

# now use -fsanitize-undefined-strip-path-components=-1
% clang++ -fsanitize=function -fsanitize=address
-fsanitize-undefined-strip-path-components=-1 $(realpath main.cpp)
% readelf -p .rodata a.out | grep main.cpp
[ 17680]  /very/long/path/main.cpp # it didn't help
```
I've also verified that the file name is not emitted to rodata when only ASAN
is used. And `-fsanitize-undefined-strip-path-components=-1` works for the
other UBSAN checks that I've used.

I was able to narrow the problem down to this block
https://github.com/llvm-mirror/clang/blob/ebb3b3ca30bc377eeebfac5e56b940f9a22b5b64/lib/CodeGen/CGExpr.cpp#L4616
Looks like -fsanize=function emits a global variable with a file name and then
ASAN instruments it. Not sure why the filename doesn't make it to the resulting
binary when ASAN is disabled.

I don't completely understand the consequences of the above-mentioned block,
but commenting it out and then rebuilding some of our binary reduses the bloat
by ~30%!

-- 
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 33562] Add a llvm-dsymutil component to the tools product

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=33562

kristof.be...@arm.com changed:

   What|Removed |Added

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

--- Comment #1 from kristof.be...@arm.com ---
I've just created the llvm-dsymutil component under tools.
Please suggest one or a few names that could be added to the "default cc" list,
i.e. people that should be able to react to new bugs being raised.

Apologies for the delay in creating 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 37587] No component for update_test_checks and other scripts

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37587

kristof.be...@arm.com changed:

   What|Removed |Added

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

--- Comment #3 from kristof.be...@arm.com ---
I went with "support scripts", as you suggested Simon.
Greg, Fangrui: I've added you to the default cc list. Let me know if you don't
like that and I'll remove you again.

-- 
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 39348] New: cplusplus.NewDeleteLeaks false positive on code using gmock

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39348

Bug ID: 39348
   Summary: cplusplus.NewDeleteLeaks false positive on code using
gmock
   Product: clang
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Static Analyzer
  Assignee: dcough...@apple.com
  Reporter: ale...@google.com
CC: llvm-bugs@lists.llvm.org

#include "gmock.h"
#include "gunit.h"

using ::testing::Return;

int n;

TEST(A, B) {
  Return(true);

  ASSERT_EQ(n, 1);
}


$ clang-tidy -checks=-*,clang-analyzer*,-clang-analyzer-optin* q.cc -extra-arg
-Xclang=-analyzer-display-progress -extra-arg
-Xclang=-analyze-function="A_B_Test::TestBody()"
ANALYZE (Syntax): q.cc A_B_Test::TestBody()
ANALYZE (Path,  Inline_Regular): q.cc A_B_Test::TestBody()
16 warnings generated.
q.cc:11:3: warning: Potential leak of memory pointed to by field 'value_'
[clang-analyzer-cplusplus.NewDeleteLeaks]
  ASSERT_EQ(n, 1);
  ^
gtest.h:2022:32: note: expanded from macro 'ASSERT_EQ'
# define ASSERT_EQ(val1, val2) GTEST_ASSERT_EQ(val1, val2)
   ^
gtest.h:2004:23: note: expanded from macro 'GTEST_ASSERT_EQ'
  ASSERT_PRED_FORMAT2(::testing::internal:: \
  ^
q.cc:9:3: note: Calling 'Return'
  Return(true);
  ^
gmock-actions.h:1121:10: note: Calling constructor for 'ReturnAction'
  return internal::ReturnAction(std::move(value));
 ^
gmock-actions.h:569:43: note: Memory is allocated
  explicit ReturnAction(R value) : value_(new R(std::move(value))) {}
  ^
gmock-actions.h:1121:10: note: Returning from constructor for
'ReturnAction'
  return internal::ReturnAction(std::move(value));
 ^
q.cc:9:3: note: Returned allocated memory
  Return(true);
  ^
Suppressed 17 warnings (2 NOLINT, 15 with check filters).


I'll try to provide a hermetic reproduction later.

-- 
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 39349] New: cannot execute scan-build-7 due to extra

2018-10-18 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39349

Bug ID: 39349
   Summary: cannot execute scan-build-7 due to extra 
   Product: Packaging
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: deb packages
  Assignee: unassignedb...@nondot.org
  Reporter: hannes.fra...@smartoptics.de
CC: llvm-bugs@lists.llvm.org

The `scan-build` perl script installed into `/usr/bin/scan-build` contains an
extra unicode-char  which trips up the perl interpreter.

To reproduce:
"deb http://apt.llvm.org/xenial/ llvm-toolchain-xenial-7 main" >
/etc/apt/sources.list.d/llvm-latest.list
apt-get update
apt-get install clang-tools-7
/usr/bin/scan-build-7

Output:

Unrecognized character \xE2; marked by <-- HERE after /]*$)/ or
<-- HERE near column 116 at /usr/bin/scan-build-7 line 1082.


Inspecting the file /usr/bin/scan-build-7 at line 1081-1083 (with e.g. vim or
less)

  $Cmd =~ /(.*\/?llvm-gcc[^\/]*$)/ or
  $Cmd =~ /(.*\/?clang[^\/]*$)/ or
  $Cmd =~ /(.*\/?ccc-analyzer[^\/]*$)/) {

shows the extra  'ZERO WIDTH SPACE' character.
If I remove this character everything works as expected.

It doesn't seem to exist inside the sources themselves, at least the ones
offered for download (https://releases.llvm.org/download.html#7.0.0), so I
guess it is a packaging-only problem.

The package downloaded is: (snips from apt-get install)
Get:1 http://apt.llvm.org/xenial llvm-toolchain-xenial-7/main amd64
clang-tools-7 amd64 1:7~svn342187-1~exp1~20180920124227.28
Setting up clang-tools-7 (1:7~svn342187-1~exp1~20180920124227.28)

-- 
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] Issue 11046 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars

2018-10-18 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org,  
j...@chromium.org, v...@apple.com, mitchphi...@outlook.com,  
xpl...@gmail.com, akils...@apple.com
Labels: ClusterFuzz Reproducible Engine-libfuzzer Proj-llvm  
Reported-2018-10-19

Type: Bug

New issue 11046 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in  
llvm_llvm-opt-fuzzer--x86_64-indvars

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11046

Detailed report: https://oss-fuzz.com/testcase?key=5692273807851520

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-indvars
Fuzz target binary: llvm-opt-fuzzer--x86_64-indvars
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address:
Crash State:
  llvm_llvm-opt-fuzzer--x86_64-indvars

Sanitizer: address (ASAN)

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


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


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


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.


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