-
-
Notifications
You must be signed in to change notification settings - Fork 475
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
sparc64: a bunch of tests are failing #1305
Comments
Is that a native SPARC host? These tests pass on my x86-64 machine with qemu-sparc64 and the SPARC cross compiler. Unfortunately, all Debian SPARC machines in the GCC compiler farm are down right now, so I have no access to real SPARC machines at the moment. Do you think there's any way to reproduce the issue in any way? |
@glaubitz is it something you could help with ? :) thanks |
These seem to be regressions with 2.32.x, 2.31.0 still builds fine:
|
Can you try again with the above change? |
I just checked out mold from git which has the above change already applied but it still fails with:
|
I just tested this as well, checked out tag
|
@sylvestre @glaubitz Can you pack the entire test output directory and share it with me if you can do that? I believe it's going to be a few hundred megabytes, so you might not be able to upload it here, though. |
Sure, here you go: https://people.debian.org/~glaubitz/mold-build-sparc64.tgz |
@glaubitz Thanks! Some executables are missing in the directories, so maybe mold crashes for some tests on your machine? If you run one of the failing test script by hand (you can just execute it because it's just a bash script), does mold crash? |
I tried running one of the shared-object files which has executable flags set:
|
I will try to bisect this now. |
I mean |
There was no script to run in this folder, just three object files. |
You may want to run |
Odd that it invokes the normal system linker:
If I remember correctly, |
You want to run the script with the build directory as the current directory. In other words, But I can see the problem now. It looks like your compiler does not support How about other tests? |
Ah, sorry the error message about |
Here are three more tests:
|
Odd, when I run the tests from the build directory individually, they pass:
But not with |
Bisecting lead me to this commit:
Is Debian maybe unbundling mimalloc? |
OK, building with |
If you have a bandwidth to work on this issue, you may want to bisect mimalloc between 2.1.2 and 2.1.6 to see what change to mimalloc broke it. mimalloc maintainers are open for pull requests, but I'm pretty sure that they are not interested in debugging and fixing a SPARC issue themselves, unfortunately. |
On Jul 24, 2024, at 9:53 AM, Rui Ueyama ***@***.***> wrote:
If you have a bandwidth to work on this issue, you may want to bisect mimalloc between 2.1.2 and 2.1.6 to see what change to mimalloc broke it. mimalloc maintainers are open for pull requests, but I'm pretty sure that they are not interested in debugging and fixing a SPARC issue themselves, unfortunately.
Does mold actually use the system mimalloc library by default over its embedded one?
I’m asking because Debian’s mimalloc is at 2.1.7 already while mold ships 2.1.6.
This would also explain why @matoro hasn’t run into this issue.
|
Unless |
On Gentoo, we do force system mimalloc for mold and our mimalloc is at 2.1.7. |
Not sure you care about this but opening in case you do
https://buildd.debian.org/status/fetch.php?pkg=mold&arch=sparc64&ver=2.32.1%2Bdfsg-2&stamp=1721122298&raw=0
Example:
The text was updated successfully, but these errors were encountered: