-
Notifications
You must be signed in to change notification settings - Fork 64
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
symbols mode not working since 1.14.1 #205
Comments
Hi, thanks for reporting this! Seems pretty serious, and likely due to the AVX2 optimization indeed. Which branch (or tarball) works when you build it from source? |
I tried to build master branch and 1.14.1tag, both work fine. |
Maybe there's something in the Arch build's CFLAGS that it's sensitive to. @felixonmars, do you have a build log/specifics on how it was built? The package info I could find seems vanilla, but maybe there are Arch-global build flags I can look at? |
I suspect this is due to something else. Maybe lf doesn't understand the REP sequence. Running with |
These options didn't help, but you're right, it's not chafa, I tried running the previous version of lf (r31) and there are no glitches, so it seems the bug was introduced in lf r32 UPD: Looks like the bug has already been fixed gokcehan/lf#1736 |
I've been racking my brain trying to figure this issue out. I'd just switched from an Nvidia gpu to AMD on my desktop, so I thought the answer lay somewhere there, but it didn't seem likely. My older laptop with nearly the exact same configuration (but intel igpu) worked fine. After reading these comments I checked my laptop and confirmed that it doesn't even support AVX2, which could be why it's been spared the issue. My desktop does support AVX2, but it's not normally something I have to be conscious of. I tried to replace Arch's chafa package with chafa-git from AUR, but that didn't resolve it, so I guess I'll just wait till the official package gets updated. |
This is proving a bit hard to track down, since the issue can't be reproduced when building from source. Do any of you know which compiler version was used to produce the faulty Chafa in Arch? |
I don't know. I would try to make a bug report on the Arch package, but new user registration is closed there at the moment. If anyone else has credentials I'd ask that they make the report for us. |
@hpjansson see my build log from the AUR package. chafa.log
|
$ gcc --version
gcc (GCC) 14.1.1 20240522
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
Thanks! Real progress: Can repro with |
Minimal repro flags: |
Pretty sure that solves it. Fix will be in the next release (next week at the latest). |
Can confirm that rebuilding |
I just released the fix in version 1.14.2. Thanks all! |
Since the new
1.14.1
release, symbols mode no longer works for me.Other modes work perfectly fine, so maybe it has something to do with the new AVX2 optims for symbols?
I'm on Arch Linux.
I'm aware that there's not a lot of info in this bug report, so do let me know if there's any information I can provide.
Probably not that helpful, but I've attached an example output below.
example output
lscpu
The text was updated successfully, but these errors were encountered: