[llvm-bugs] Issue 9973 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in Db::parseTemplateArg

[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 Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2018-08-19

Type: Bug

New issue 9973 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer:  
Stack-overflow in Db::parseTemplateArg

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

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

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

Crash Type: Stack-overflow
Crash Address: 0x7ffd5bcc0f28
Crash State:
  Db::parseTemplateArg

Sanitizer: address (ASAN)

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


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


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

[llvm-bugs] [Bug 38632] New: wasm32: atomic_notify intrinsic disagrees with Gecko/wabt implementations

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=38632

Bug ID: 38632
   Summary: wasm32: atomic_notify intrinsic disagrees with
Gecko/wabt implementations
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: WebAssembly
  Assignee: unassignedb...@nondot.org
  Reporter: a...@crichton.co
CC: dan433...@gmail.com, llvm-bugs@lists.llvm.org

Currently the `llvm.wasm.atomic.notify` intrinsic in LLVM looks like:

declare i64 @llvm.wasm.atomic.notify(i32*, i64)

notable taking i64 for a number of waiters to wake up and returning an i64 for
the number of waiters notified. While this agrees with the current proposed
spec [1] it looks like it disagrees with wabt [2] and with Gecko's
implementation (I got validation errors in Firefox nightly).

Is this something that LLVM needs to update? Or should the spec be updated to
use i32?

[1]:
https://github.com/WebAssembly/threads/blob/master/proposals/threads/Overview.md
[2]:
https://github.com/WebAssembly/wabt/blob/ffe92e6c57fe0ee356c5ae98d0ef0ac6ecfdee27/src/opcode.def#L382

-- 
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