If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I also use Windows 8.1 for gaming and Mac OS X and can sure tell you that the rest of the world doesn't care. Mac apps are huge. Windows games are huge. The binaries are huge. Nothing is optimized well. Windows updater for Java doesn't delete old versions and the C: drive can be filled with 50 versions of Java 5 and 60 versions of Java 6. Nobody cares. On top of that they constantly run antivirus software which slows down the machine.
We care. One might ask why you're on a Linux forum if your philosophy is so different.
I think you posted the list in another thread. But have you posted it to GCC bugzilla?
No. AFAIK they need easily testable small example that exhibits the error. This means that I was expected to sit down, understand what's going on and reduce bazillion files to one of a few lines.
I didn't have the time nor knowledge for such things.
And have I just showed them whole package in the report, what good would that do ? They must have known things aren't 100% peachy since so many packages failed.
And without doing the journey myself I'd just report what they already know - not all packages compile with LTO. And list of those was not shrinking, so they obviously haven't been investing work into this directly and one or a few more package names wouldn't mean a thing.
One can care about linux and still not care about what you specifically care.
I use Linux because it's great for servers, embedded and development desktops, but most games only work on Windows and Macs are great when travelling since their power consumption is low (only on Mac OS X), great UI/UX, great looks, good quality, nice.
It is still basically what I described earlier though. The kernel simply does not need floating point arithmetic. Sometimes, vector instructions are useful, but in those times, we use critical sections. Anyway, few kernel developers ever use these functions.
yes, floating point is banned from the kernel for a couple reason
one being just that, that its behavior is dependent on some flags (and they are cpu wide)
can't edit http://wiki.osdev.org/SSE better explains what needs to be done
also i'm not 100% about how userspace floating point is handled, never had problems with it (tbh never needed to change the state, so..)