compiler-bugs's Introduction

compiler-bugs

A collection of bug reports I made for various Fortran compilers.

The HPC Bug Reproducers repository has some good advice on what to include in a bug report:

When creating a report/reproducer, at minimum a README.md file should be included in the folder. The README should contain the following information:

The version(s) of the tool and the environment(s) in which it malfunctions

Point to additional content in the folder necessary to reproduce the issue

Detailed description of the steps needed to reproduce the issue

(optional) A description for how to work around the issue

Any other source code, input files, etc. should also be included in the created folder sufficient for an independent contributor to reproduce the encountered issue.

Also see John Regehr's advice:

To show people that you have found a compiler bug, you need to create a bug report that is convincing, reproducible, and actionable. You need a small test case (2-3 lines is ideal) that is obviously free of undefined behavior, obviously independent of unspecified behavior, and obviously miscompiled. Creating small failure-inducing test cases is hard work. You also need to provide the expected result, and perhaps give a list of compilers and options that produce that result. Third, you need to clearly identify the version of the compiler that produces the wrong result, including the target CPU and OS, the options used to build the compiler, etc. If the compiler is a patched one supplied by an OS vendor (as in the Ubuntu example above), you should say so.