zhanchangbao-sanechips commented on code in PR #2644:
URL: https://github.com/apache/orc/pull/2644#discussion_r3433384153


##########
.github/workflows/build_and_test.yml:
##########
@@ -63,6 +63,38 @@ jobs:
         cd docker
         ./run-one.sh local main ${{ matrix.os }}
 
+  riscv64:
+    name: "RISC-V ${{ matrix.os }}"
+    needs: [license-check]
+    runs-on: ubuntu-latest
+    timeout-minutes: 180
+    strategy:
+      fail-fast: false
+      max-parallel: 20
+      matrix:
+        os:
+          - riscv64-ubuntu26
+    steps:
+    - name: Checkout
+      uses: actions/checkout@v6
+    - name: Set up QEMU
+      uses: docker/setup-qemu-action@v3
+      with:
+        platforms: linux/riscv64
+    - name: Set up Buildx
+      uses: docker/setup-buildx-action@v3
+    - name: Build Docker image
+      run: |
+        cd docker/${{ matrix.os }}
+        docker buildx build --platform linux/riscv64 --load \
+          --cache-from type=gha,scope=riscv64-ubuntu26 \
+          --cache-to type=gha,mode=max,scope=riscv64-ubuntu26 \
+          -t orc-riscv64 .
+    - name: Build ORC with RVV
+      run: |
+        docker run --platform linux/riscv64 --rm -v $(pwd):/root/orc 
orc-riscv64 /bin/bash -c \

Review Comment:
   > we should make sure v extension is enable
   
   I have updated the docker run command to include the environment variable 
QEMU_CPU=rv64,v=on,vlen=128,vext_spec=v1.0, and verified that RVV is working 
correctly.
   
   The vext_spec=v1.0 explicitly specifies the vector extension version to 
suppress the warning: "vector version is not specified, use the default value 
v1.0".
   
   <img width="1668" height="1039" alt="PixPin_2026-06-18_11-01-21" 
src="https://github.com/user-attachments/assets/183654a6-da61-466d-b7d9-c25c25074a8a";
 />



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to