https://bugs.kde.org/show_bug.cgi?id=447184

--- Comment #6 from Vladimir Dergachev <volo...@mindspring.com> ---
On Fri, 14 Apr 2023, Nate Graham wrote:

> https://bugs.kde.org/show_bug.cgi?id=447184
>
> Nate Graham <n...@kde.org> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>         Resolution|WAITINGFORINFO              |FIXED
>             Status|NEEDSINFO                   |RESOLVED
>
> --- Comment #5 from Nate Graham <n...@kde.org> ---
> Yep, I don't experience the bug with that .desktop file pinned to my Task
> Manager. So let's call it fixed!

Agreed !

>
> It's always possible to compile a new Plasma on an old distro, but the older
> the distro, the harder it will be since Plasma frequently depends on 
> relatively
> new versions of 3rd-party libraries. I'd file it under "possible but painful"
> (or adventurous, depending on how you want to look at it!).
>
> Also JFYI you probably need to be testing your code for speed and correctness
> with new tooling as well as old tooling, because you can't guarantee that all
> of your users will be using software compiled with old tooling, unless you
> distribute the software yourself in purely binary form. As long as the source
> code is available, any random distro can compile it with any tooling and
> package it up for consumption.

No, no, this is a different situation - this is a numerical code and 
speed is critical, so one needs to control assembly output. So I want the 
C compiler to produce a binary where inner loops do exactly what I want.

When you upgrade distros gcc and C libraries often have large changes. A 
lot of those changes are well-intentioned attempts to automatically secure 
programs against bugs or introduce speedups into poorly optimized 
programs, at the expense of numerical codes such as mine. So I compare 
runtime between different binaries and start digging into assembly to 
figure out what went wrong.

This fine tuning is worthwhile because the code takes months to run.  It 
is the results that are distributed to the users - they are portable and 
use MVL library (package RMVL if you use R).

thank for looking into this !

Vladimir Dergachev

>
> -- 
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to