llnl / llnl/AutoParBench

Survey Question on the For loop in source file benchmarks/Cetus/dataracebench/DRB005-indirectaccess1-orig-yes.c line 139

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
12
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Hello Sir/ Madam
We are from a research group at Iowa State University, USA. We want to do a survey on Github developers on the methods they used for paralleling their code. To do the survey, We want to ask three questions:

1. Have you ever tried to add pragma for that 'for' loop?.

2. How much confidence do you have about the correctness of this implementation? You can choose from 1-5 with 1 as the lowest confidence score and 5 as the highest confidence.

3. (Optional) Do you actually run (interpret the code with compilation and pass input/get output) the code? Yes/No
- If yes, can you provide the information of what are the input and expected output of this program (the input that caused the program to run through this for-loop).

The for loop is from line 139 of file https:/github.com/LLNL/AutoParBench/blob/master/benchmarks/Cetus/dataracebench/DRB005-indirectaccess1-orig-yes.c
Here is a part of the code:

nan
for (i = 0; i < 180; ++i)
{
int idx = indexSet[i];
xa1[idx] += 1.0 + i;
xa2[idx] += 3.0 + i;
}

Sincerely thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with benchmarks/Cetus/dataracebench/DRB005-indirectaccess1-orig-yes.c at line 139 and review the referenced loop. The issue asks developers to answer survey questions rather than change the repository, so confirm with the maintainers whether a documented response is wanted; done would mean providing the requested survey information, not a code contribution.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
testing
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.