You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The graphite use flag does not change the default behavior of the gcc compiler, as the graphite functionality needs to be explicitly enabled to have any effect.
However, I would like to experiment with using the graphite loop optimizations to see if I can get some better performance out of specific packages on my gentoo-on-rpi-64bit installation.
If the graphite useflag was enabled on the binhost, it would have a very small increase in compile-times on the binhost, but would save anyone who wants to experiment with graphite from very long (multiple days..?) compile times.
The text was updated successfully, but these errors were encountered:
30 Oct 2020: sadly, due legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the images may be of use still in certain applications); however, there will be no further updates to the underlying binhost etc., nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.
The graphite use flag does not change the default behavior of the gcc compiler, as the graphite functionality needs to be explicitly enabled to have any effect.
However, I would like to experiment with using the graphite loop optimizations to see if I can get some better performance out of specific packages on my gentoo-on-rpi-64bit installation.
If the graphite useflag was enabled on the binhost, it would have a very small increase in compile-times on the binhost, but would save anyone who wants to experiment with graphite from very long (multiple days..?) compile times.
The text was updated successfully, but these errors were encountered: