Show Idle (> d.) Chans


Results 1 ... 9 found in asciilifeform for 'gcc5'

dulapbot: (trilema) 2018-09-05 asciilifeform: upstack, https://archive.is/WMoLv (warning: entomologists only) << the how&why of uboot 'gcc5+ only' idjicy. tldr: gcc5 silently broke uboot on arm. so the latter was 'fixed' so as to... ONLY gcc5+. in the now-customary way.
dulapbot: (trilema) 2019-01-19 asciilifeform: the gcc5+ gnomes, occupy selves with cranking out 'mandatory' kludges for intelism; removing backend support for vintage, marginally-sane archs (alpha, hitachi, etc); gluing-with-broken-glass various incompatibilities to prevent coad developed under 5+ from building under 4.x; inserting 'optimizations' that snake around naive cprogrammer attempts at bounds-constraint; and so forth.
dulapbot: (trilema) 2019-04-22 asciilifeform: trinque: speaking moar from concrete than theoretical pov -- gcc5 has documented 'optimizations' that remove bounds checks
asciilifeform: the latter is fulla 'surprises'.
asciilifeform wonders whether thing expects gcc5+
asciilifeform: well not overlay, but ideally wholesale fork of gentoo. incl. banishment of gcc5+, python3, etc
asciilifeform: fwiw contrary to asciilifeform's expectation -- did not need to resort to gcc5 or later for any package (tho is possible to eselect and use evil gcc if req'd; evil-gcc's do build w/ godly one )
asciilifeform: it aint 'ecologically clean' (i.e. not musltronic, or especially compact) but at very least free of poettering/gcc5.
asciilifeform: gcc per se was artfully sabotaged over decade+ into ~unusability . and imho rms & co are ~entirely~ to blame.