Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[spec cint2k] 253.perlbmk needs to be run 4 times #691

Closed
llvmbot opened this issue Apr 18, 2004 · 1 comment
Closed

[spec cint2k] 253.perlbmk needs to be run 4 times #691

llvmbot opened this issue Apr 18, 2004 · 1 comment
Labels
duplicate Resolved as duplicate

Comments

@llvmbot
Copy link
Member

llvmbot commented Apr 18, 2004

Bugzilla Link 319
Resolution DUPLICATE
Resolved on Feb 22, 2010 12:48
Version trunk
OS Linux
Blocks #690
Reporter LLVM Bugzilla Contributor

Extended Description

The perl benchmark needs to be run 4 times as there are really 4 tests which are
all separate scripts, each with its own set of input/output files.

This means that 175.vpr is not the only one that nees to be run multiple times.
We should make our SPEC test runner more generic to allow for this.
@lattner
Copy link
Collaborator

lattner commented Apr 18, 2004

We only need one bug for this...

*** This bug has been marked as a duplicate of 317 ***

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 1, 2021
@Quuxplusone Quuxplusone added the duplicate Resolved as duplicate label Jan 20, 2022
pysuxing pushed a commit to pysuxing/llvm-project that referenced this issue Jul 17, 2024
@sitio-couto @lanza
[CIR][ABI] Replay TargetLowering library reverted commits (llvm#697)
361107d 
Essentially re-applies llvm#668 and llvm#678, but also includes llvm#687 which
patched build introduced by the other two PRs.

Closes llvm#691
keryell pushed a commit to keryell/llvm-project that referenced this issue Oct 19, 2024
@sitio-couto @lanza
[CIR][ABI] Replay TargetLowering library reverted commits (llvm#697)
884d069 
Essentially re-applies llvm#668 and llvm#678, but also includes llvm#687 which
patched build introduced by the other two PRs.

Closes llvm#691
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate Resolved as duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Quuxplusone @lattner @llvmbot