[flang-dev] Contributing unit tests from DOE science codes

[Finkel, Hal J. via flang-dev]

Hi, Nick,

>  One thing that I should clarify is that I am focused on submitting *only* the llvm-lit test that exposes the issue.

I think that if it's just the test, then bugzilla is best.

 -Hal

Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory

________________________________
From: Romero, Nichols A. <naromero at anl.gov>
Sent: Friday, May 15, 2020 3:02 PM
To: flang-dev at lists.llvm.org <flang-dev at lists.llvm.org>
Cc: McCormick, Pat <pat at lanl.gov>; Finkel, Hal J. <hfinkel at anl.gov>
Subject: Contributing unit tests from DOE science codes


Hi,



I am part of the DOE ECP Flang project and work for Hal and Pat. One of my tasks on the project is to harden the Flang front-end w.r.t. DOE science codes. It was recommended to me that I create tests when I encounter one of these issues and submit them.



An example of one is here:

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



Do the Flang developer’s recommend that I submit the llvm-lit test in a Bugzilla issue report or submit it via Phabricator?  One thing that I should clarify is that I am focused on submitting *only* the llvm-lit test that exposes the issue. While it might be possible in the future to get up to speed with the Flang front-end code and actually fix the front-end issues, my role on the ECP project is primarily as a tester at the moment.



--

Nichols A. Romero, Ph.D.

Computational Science Division

Argonne Leadership Computing Facility
Argonne National Laboratory
Building 240 Room 2-127
9700 South Cass Avenue
Lemont, IL 60439
(630) 252-3441


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/flang-dev/attachments/20200515/0abc71ec/attachment-0001.html>