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.

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

Running 483.xalancbmk in SPEC 2006 with error #1883

Open
Ye-Jinhong opened this issue Dec 22, 2024 · 1 comment
Open

Running 483.xalancbmk in SPEC 2006 with error #1883

Ye-Jinhong opened this issue Dec 22, 2024 · 1 comment

Comments

@Ye-Jinhong
Copy link

Ye-Jinhong commented Dec 22, 2024

Description

I am trying to running spec 2006 int part with spike, but came across an error when running 483.xalancbmk.

Fatal Error.Occurred at unknown file, line 0, column{null}.An exception occurred! Type:XMLPlatformException, Message:Could not determine base pathname of the file
SAXParseException: An exception occurred! Type:XMMLPlatformException, Message:Could not determinebase pathname of the file (, line 0, column 0)

It seems that program can't find the specific file given by command.

Reproduce

Steps

  1. build riscv-tool-chain and spike
  2. bind sys_futex(98) with no-op and build pk
  3. build SPEC2006 with riscv-tool-chain(riscv64-unknow-linux-gnu-, -static, -O3, -fno-strict-aliasing)
  4. running with
cd /path/to/SPEC/483.xalancbmk/run/run_base_ref_label.0000
/path/to/spike /path/to/pk Xalan_base.label -v t5.xml xalanc.xsl

Others

I used to figure out that is the GCC14.2 cause wrong? And try GCC13 to compile SPEC2006, it doesn't work. However, for GCC13 compiling SPEC, Gem5 can runing xalancbmk without any error.

So for me, a new starter in spike, have no idea to fix this.

@eriktai
Copy link

eriktai commented Feb 25, 2025

One thing I can hint is about a command called realpath(char* filename, char* absPath), which returns NULL, although the result, absolute path, is correct. However, this should be investigated further to reproduce the result and discern the root cause. SPEC source code is a intellectual property so I suggest trying to find the root cause and put smaller code sections that didn't related to SPEC on here.

Regarding debugging, you can try to use the gdb to debug. The steps are described in README, ignoring the nostartfile part. It's very simple. Besides, putting inf-loop before and after the main code is a more recommended method to halt the spike.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants