25a9c73901
* Don't use HTML comments, as they are noisy, which makes the templates more intimidating. * Use "TODO" to clearly demarcate everywhere the issue reporter should fill in some information. * Use headers and white space abundantly, which makes it easier to visually process the template and its sections at a glance, and less of an intimidating wall of text. Fixes #2661
44 lines
722 B
Markdown
44 lines
722 B
Markdown
---
|
|
name: Cranelift Bug report
|
|
about: Report a bug or a crash in Cranelift.
|
|
title: 'Cranelift: '
|
|
labels: bug, cranelift
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
Thanks for filing an issue! Please fill out the TODOs below.
|
|
|
|
### `.clif` Test Case
|
|
|
|
```
|
|
TODO: paste .clif test case here. Ideally, a test case that has been reduced via
|
|
the `clif-util bugpoint` command.
|
|
```
|
|
|
|
### Steps to Reproduce
|
|
|
|
* TODO: First, ...
|
|
* TODO: Then, ...
|
|
* Etc...
|
|
|
|
### Expected Results
|
|
|
|
TODO: What do you expect to happen?
|
|
|
|
### Actual Results
|
|
|
|
TODO: What actually happens? Panic? Segfault? Incorrect result?
|
|
|
|
### Versions and Environment
|
|
|
|
Cranelift version or commit: TODO
|
|
|
|
Operating system: TODO
|
|
|
|
Architecture: TODO
|
|
|
|
### Extra Info
|
|
|
|
Anything else you'd like to add?
|