Skip to content

[RISCV] Don't forward AVL in VSETVLIInfo if it would clobber other definitions #11925

[RISCV] Don't forward AVL in VSETVLIInfo if it would clobber other definitions

[RISCV] Don't forward AVL in VSETVLIInfo if it would clobber other definitions #11925

Workflow file for this run

name: "Add buildbot information to first PRs from new contributors"
permissions:
contents: read
on:
# It's safe to use pull_request_target here, because we aren't checking out
# code from the pull request branch.
# See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
pull_request_target:
types:
- closed
jobs:
buildbot_comment:
runs-on: ubuntu-latest
permissions:
pull-requests: write
if: >-
(github.repository == 'llvm/llvm-project') &&
(github.event.pull_request.merged == true)
steps:
- name: Checkout Automation Script
uses: actions/checkout@v4
with:
sparse-checkout: llvm/utils/git/
ref: main
- name: Setup Automation Script
working-directory: ./llvm/utils/git/
run: |
pip install --require-hashes -r requirements.txt
- name: Add Buildbot information comment
working-directory: ./llvm/utils/git/
run: |
python3 ./github-automation.py \
--token '${{ secrets.GITHUB_TOKEN }}' \
pr-buildbot-information \
--issue-number "${{ github.event.pull_request.number }}" \
--author "${{ github.event.pull_request.user.login }}"