Search
146 results for “gnutools”
-
@sysedit In general, I totally can relate you your statement.
However, there is one additional notion to it: if you're using a really(!) powerful and flexible tool, you might need less tool switches for slightly different jobs.
IMO that's one of the (meta-)reasons why there are so many Windows programs out there: normal users aren't using flexible tools like #GNUtools (UNIX pipes) or #Emacs that are able to match a wide range of requirements where "normal people" are using a specific tool for one specific use-case.
I see the tendency that, e.g., every app needs to have a "read later/notify me later" feature or its own spell checker and so forth. From a tech perspective, this is not very clever.
If you do have your flexible #knowledgemanagement tool, you can implement all sorts of "do stuff later" functionality with it, in case your tools are flexible enough to interact with each other.
Furthermore: our requirements differ more than we think: https://karl-voit.at/2021/01/18/tool-choices/
-
@sysedit In general, I totally can relate you your statement.
However, there is one additional notion to it: if you're using a really(!) powerful and flexible tool, you might need less tool switches for slightly different jobs.
IMO that's one of the (meta-)reasons why there are so many Windows programs out there: normal users aren't using flexible tools like #GNUtools (UNIX pipes) or #Emacs that are able to match a wide range of requirements where "normal people" are using a specific tool for one specific use-case.
I see the tendency that, e.g., every app needs to have a "read later/notify me later" feature or its own spell checker and so forth. From a tech perspective, this is not very clever.
If you do have your flexible #knowledgemanagement tool, you can implement all sorts of "do stuff later" functionality with it, in case your tools are flexible enough to interact with each other.
Furthermore: our requirements differ more than we think: https://karl-voit.at/2021/01/18/tool-choices/
-
@sysedit In general, I totally can relate you your statement.
However, there is one additional notion to it: if you're using a really(!) powerful and flexible tool, you might need less tool switches for slightly different jobs.
IMO that's one of the (meta-)reasons why there are so many Windows programs out there: normal users aren't using flexible tools like #GNUtools (UNIX pipes) or #Emacs that are able to match a wide range of requirements where "normal people" are using a specific tool for one specific use-case.
I see the tendency that, e.g., every app needs to have a "read later/notify me later" feature or its own spell checker and so forth. From a tech perspective, this is not very clever.
If you do have your flexible #knowledgemanagement tool, you can implement all sorts of "do stuff later" functionality with it, in case your tools are flexible enough to interact with each other.
Furthermore: our requirements differ more than we think: https://karl-voit.at/2021/01/18/tool-choices/
-
@sysedit In general, I totally can relate you your statement.
However, there is one additional notion to it: if you're using a really(!) powerful and flexible tool, you might need less tool switches for slightly different jobs.
IMO that's one of the (meta-)reasons why there are so many Windows programs out there: normal users aren't using flexible tools like #GNUtools (UNIX pipes) or #Emacs that are able to match a wide range of requirements where "normal people" are using a specific tool for one specific use-case.
I see the tendency that, e.g., every app needs to have a "read later/notify me later" feature or its own spell checker and so forth. From a tech perspective, this is not very clever.
If you do have your flexible #knowledgemanagement tool, you can implement all sorts of "do stuff later" functionality with it, in case your tools are flexible enough to interact with each other.
Furthermore: our requirements differ more than we think: https://karl-voit.at/2021/01/18/tool-choices/
-
I'm looking for a new #gnutools job; long story short, my current employer is pushing me to retire early as part of a division-wide "reorganization", but I want to keep working. I'm a current #gcc and #binutils maintainer and have also contributed to #gdb, #glibc, #newlib, and #qemu. Lately I've been working on adding GCC front-end support for #openmp, but I've also done back-end things for multiple architectures, and I write documentation. DM me for more details and contact info.
-
I'm looking for a new #gnutools job; long story short, my current employer is pushing me to retire early as part of a division-wide "reorganization", but I want to keep working. I'm a current #gcc and #binutils maintainer and have also contributed to #gdb, #glibc, #newlib, and #qemu. Lately I've been working on adding GCC front-end support for #openmp, but I've also done back-end things for multiple architectures, and I write documentation. DM me for more details and contact info.
-
I'm looking for a new #gnutools job; long story short, my current employer is pushing me to retire early as part of a division-wide "reorganization", but I want to keep working. I'm a current #gcc and #binutils maintainer and have also contributed to #gdb, #glibc, #newlib, and #qemu. Lately I've been working on adding GCC front-end support for #openmp, but I've also done back-end things for multiple architectures, and I write documentation. DM me for more details and contact info.
-
I'm looking for a new #gnutools job; long story short, my current employer is pushing me to retire early as part of a division-wide "reorganization", but I want to keep working. I'm a current #gcc and #binutils maintainer and have also contributed to #gdb, #glibc, #newlib, and #qemu. Lately I've been working on adding GCC front-end support for #openmp, but I've also done back-end things for multiple architectures, and I write documentation. DM me for more details and contact info.
-
I'm looking for a new #gnutools job; long story short, my current employer is pushing me to retire early as part of a division-wide "reorganization", but I want to keep working. I'm a current #gcc and #binutils maintainer and have also contributed to #gdb, #glibc, #newlib, and #qemu. Lately I've been working on adding GCC front-end support for #openmp, but I've also done back-end things for multiple architectures, and I write documentation. DM me for more details and contact info.
-
.@IntelDevTools #AMX-COMPLEX Support Added To #GNU @gnutools Binutils
https://www.phoronix.com/news/Intel-AMX-COMPLEX-GNU-Binutils
Original tweet : https://twitter.com/phoronix/status/1644281513268203520
-
.@IntelSoftware @IntelDevTools Adds "#EmeraldRapids" Support To The @gnutools #GCC 13 Compiler
https://www.phoronix.com/news/GCC-13-Initial-Emerald-Rapids
Original tweet : https://twitter.com/phoronix/status/1610597431451979776
-
#Intel RAO-INT Added To @gnutools #GCC 13, #GrandRidge & #GraniteRapids CPU Targets Ready
https://www.phoronix.com/news/Intel-RAO-INT-Grand-Granite
Original tweet : https://twitter.com/phoronix/status/1589565107457396736
-
#Intel RAO-INT Added To @gnutools #GCC 13, #GrandRidge & #GraniteRapids CPU Targets Ready
https://www.phoronix.com/news/Intel-RAO-INT-Grand-Granite
Original tweet : https://twitter.com/phoronix/status/1589565107457396736
-
#Intel RAO-INT Added To @gnutools #GCC 13, #GrandRidge & #GraniteRapids CPU Targets Ready
https://www.phoronix.com/news/Intel-RAO-INT-Grand-Granite
Original tweet : https://twitter.com/phoronix/status/1589565107457396736
-
.@Intel #GraniteRapids Support Submitted For The @gnutools #GCC Compiler
-- Nice seeing Intel having primed Granite Rapids, Sierra Forest, and Grand Ridge for GCC 13. That's the same version where AMD is introducing (belated) Znver4 support.
https://www.phoronix.com/news/Intel-Granite-Rapids-GCC
Original tweet : https://twitter.com/phoronix/status/1588474179338514432
-
.@Intel #GraniteRapids Support Submitted For The @gnutools #GCC Compiler
-- Nice seeing Intel having primed Granite Rapids, Sierra Forest, and Grand Ridge for GCC 13. That's the same version where AMD is introducing (belated) Znver4 support.
https://www.phoronix.com/news/Intel-Granite-Rapids-GCC
Original tweet : https://twitter.com/phoronix/status/1588474179338514432
-
.@Intel #GraniteRapids Support Submitted For The @gnutools #GCC Compiler
-- Nice seeing Intel having primed Granite Rapids, Sierra Forest, and Grand Ridge for GCC 13. That's the same version where AMD is introducing (belated) Znver4 support.
https://www.phoronix.com/news/Intel-Granite-Rapids-GCC
Original tweet : https://twitter.com/phoronix/status/1588474179338514432
-
CW: (Desde Twitter)
The @[email protected] #GCC 10 Lands Support For Targeting #TI's 32-bit #PRU Processor https://www.phoronix.com/scan.php?page=news_item&px=GCC-10-TI-PRU-Target
-
Inspired by a short article called "I like Makefiles" I have adapted my #Bootstrap5 #SCSS template to make use of the Make tool, and it's cool 🙂
I'm gonna use it more often for other projects.#GNUtools #webdev
🌐 Project repository: https://codeberg.org/amarok24/template_bootstrap5_sass_php
📝 Link to the mentioned article: https://switowski.com/blog/i-like-makefiles/ -
#Arm Scalable Matrix Extension 2 "#SME2" Support Lands In @gnutools Binutils
https://www.phoronix.com/news/Arm-SME2-GNU-Binutils
Original tweet : https://twitter.com/phoronix/status/1641388766525784065
-
.@AmpereComputing #AmpereOne Sees Last Minute Compiler Tuning Ahead Of @gnutools #GCC 13
https://www.phoronix.com/news/AmpereOne-Costs-GCC-13
Original tweet : https://twitter.com/phoronix/status/1640363625369018372
-
.@IntelDevTools Sends Out #MeteorLake & #SierraForest Patches For The @gnutools #GCC Compiler
-- Great seeing @IntelSoftware @OpenAtIntel continue in their early enablement work with #opensource compilers for new x86_64 instructions & future CPUs!!
https://www.phoronix.com/news/Intel-GCC-MTL-Sierra-Forest
Original tweet : https://twitter.com/phoronix/status/1580862790121979904
-
Yesterday @SUSE published our paper "Advanced Optimization and New Capabilities of GCC 10:" https://documentation.suse.com/sbp/all/pdf/SBP-GCC-10_color_en.pdf
I hope most of it is useful and interesting for all #gnutools users. We recommend optimization options, discuss LTO, PGO and look at speeding up SPEC and #Firefox.
