-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add PNG support to the example apps #3
Comments
This is finally in, and will be in the next release. (feel free to play with it in the master branch) |
The arch aur package fails to build Who is to fix this, should the maintainer change the building process or can libavif even solve this? |
That's a weird one. I'm not a fan of libpng's choice to use setjmp(), but flow-wise, I think rowPointers is safe here. It is initialized to NULL before any longjmp is possible, and any call to longjmp eventually ends up at the cleanup label, which handles either state of rowPointers correctly. Can you give me your compiler version? I'd like to repro the error here and see if I can come up with a proper solution in libavif. |
The Internet (tm) suggests I can flag anything that might get jumped over as volatile as a hint to the optimizer to not do odd things with it. That might be enough. I want to see it fix the warning myself though. |
Nevermind, I repro'd with the archlinux Docker image. I'll fix it. |
Sorry you were too fast for me to respond on this one |
I think this will fix it, give it a shot. |
It did indeed fix it! |
Sorry to add something else to this
I might look into this myself when I have time, but seems like something in libpng is not quite sorted correctly |
Yuck, it is my fault. |
Okay, I reverted that change and put a new one in. |
Yes, now it works, thank you! |
As a note, I just fixed 16bpc PNG writing, my call to |
Something still seems odd about reading/writing png avifenc --max 0 in.png out.avif identify -verbose says amongst other differences
|
Understood, thanks for the clarification |
@utack I believe I may have done you a bit of a disservice by not being clearer in my response. I've recently had a discussion here which started from my quote above: That reply should not only give you much more context about what I meant here, but also some hints as to avoid this issue in the future (with a more recent libavif / avifenc). Cheers! |
Thank you @joedrago I have followed it! |
This would be handy for testing
The text was updated successfully, but these errors were encountered: