Results 1 ... 92 found in all logged channels for 'gcc5'
(pest) asciilifeform: (afaik there aint currently a good 1-page summary of gcc5ism)
(pest) asciilifeform: famously gcc5 snips out crypto zeroizations
(pest) hapax: asciilifeform: yeah, i got the "use <gcc5" from you guys
(pest) asciilifeform: ^ last version used by asciilifeform , as immediately after that one, was catastrophically broken in various ways
(asciilifeform) dulapbot: Logged on 2022-06-02 19:43:08 asciilifeform: verisimilitude: fwiw asciilifeform tuned outta 'new gnat' when it went gcc5+
(asciilifeform) asciilifeform: verisimilitude: fwiw asciilifeform tuned outta 'new gnat' when it went gcc5+
(asciilifeform) asciilifeform: verisimilitude: gcc5 will arbitrarily decide that bounds checks against exploitable overflow, memset to wipe secrets from process memory, etc. 'redundant' and silently remove.
(asciilifeform) 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.
(asciilifeform) dulapbot: (trilema) 2017-06-02 asciilifeform: on top of this, gcc5 happily removes , e.g., memset
(pest) billymg: the one (luckily) dropped line, right after this line: <asciilifeform>: signpost: actually last asciilifeform knew, kernel used 0 gcc5isms or anyffin of the kind. would actually be surprised if didn't build w/ tcc even nao w/out heavy massage.
(pest) asciilifeform: http://logs.bitdash.io/pest/2022-01-26#1003094 << to asciilifeform loox like a 'smoking gun' gcc5ism (but unsurprisingly author dun fess up to it)
(asciilifeform) 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.
(asciilifeform) 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.
(asciilifeform) dulapbot: (trilema) 2019-04-22 asciilifeform: trinque: speaking moar from concrete than theoretical pov -- gcc5 has documented 'optimizations' that remove bounds checks
(asciilifeform) asciilifeform wonders whether thing expects gcc5+
(asciilifeform) asciilifeform: well not overlay, but ideally wholesale fork of gentoo. incl. banishment of gcc5+, python3, etc
(asciilifeform) 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) asciilifeform: it aint 'ecologically clean' (i.e. not musltronic, or especially compact) but at very least free of poettering/gcc5.
(asciilifeform) asciilifeform: gcc per se was artfully sabotaged over decade+ into ~unusability . and imho rms & co are ~entirely~ to blame.
(trilema) asciilifeform: trinque: speaking moar from concrete than theoretical pov -- gcc5 has documented 'optimizations' that remove bounds checks
(trilema) asciilifeform really must dust off the old notes and try this with own hands; the presence of gcc5 in the build bothers asciilifeform not only from 'practical' but from thompsonistic pov
(trilema) asciilifeform: !#s from:trinque gcc5
(trilema) asciilifeform: spyked: i admit that i still dunget why it needs the gcc5 step
(trilema) asciilifeform indeed expected that it's 100% gcc5ism
(trilema) bvt: ran the tests for exceptions race, libgcc is fine in gcc4.9, locks are in place, so it seems that it is indeed another gcc5ism
(trilema) asciilifeform: mircea_popescu: imho the near-term thing to do is for bvt to get the gcc5sim, glibcism, out of his test setup. then can proceed to fix bugs that we actually have in the house, rather than liquishit that only afflicts glibctards.
(trilema) mircea_popescu: around gcc5 times (early 2016) binutils were verschlimmbessert with support of new relocations <<< aaahahahahaha.
(trilema) bvt: i don't think it gcc5-specific, the patch against this problem that i've seen was written for gcc 4.8
(trilema) diana_coman: bvt, interesting; is that gcc5-specific though?
(trilema) asciilifeform suspects this is a gcc5ism
(trilema) asciilifeform: afaik there is exactly 0 win from gcc5+, and plenty of lose.
(trilema) asciilifeform: maybe musl implements some functionality is a way unexpected << where didja get a gcc5istic gnat built on musl, bvt ??
(trilema) asciilifeform: i recommend to leave gcc5 entirely alone (unless specifically digging for lulz)
(trilema) asciilifeform: gcc5 breakage extends into the Ada world << noshit, if yer on a gcc5istic gnat, all bets are off, they fucked the back end
(trilema) asciilifeform: ( if yer using a heathen gnat, and a gcc5+istic one, it will output the familiar gcc5isms; but we aint using one )
(trilema) asciilifeform: not having used gcc5+ , i never saw this bug
(trilema) 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.
(trilema) asciilifeform: http://btcbase.org/log/2019-01-05#1884619 << from ave1 , i hope to see a 'port' of tmsr-gnat that can be hard-welded into cuntoo as primary gcc ( to remove the hack where it builds gcc5, then down to 4.9, and neither of'em being a gnat )
(trilema) asciilifeform: ( also to stop the gcc5ism gangrene, but this is a close second )
(trilema) 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.
(trilema) asciilifeform: i.e. i was not able to build uboot on ANY of my boxen, even on the toilets where gcc5+ exists
(trilema) asciilifeform: hmm, why does it emerge gcc5 ???
(trilema) asciilifeform: spyked: this looks like classic gcc5ism
(trilema) asciilifeform: http://btcbase.org/log/2018-01-21#1773685 << if this is about the 'integer retardation' issue, the 1 thing it quite definitively had 0 to do with , is gcc5 : which did not exist in the era of 0.5.3 , nor did it exist in my stator or rotor setups
(trilema) a111: Logged on 2018-01-21 21:38 trinque: my current wager is folks that had it were using a gcc5, which is defaulted to a later standard for C
(trilema) trinque: my current wager is folks that had it were using a gcc5, which is defaulted to a later standard for C
(trilema) asciilifeform: in other noose, trinque's pill worked, but the gcc5.x item was not needed
(trilema) asciilifeform: tbh the retardation of gcc5+ dun affect , in any known way, ada -- the rotters rotted c/cpp frontend strictly
(trilema) asciilifeform: mircea_popescu: principal headache is in re bringing up ~new~ boxes, without gcc5+ crapolade leaking in; rather than keeping old ones going
(trilema) a111: Logged on 2017-11-25 01:55 asciilifeform: http://btcbase.org/log/2017-11-25#1742977 << having python > 2.7 is quite like having gcc5 around.
(trilema) asciilifeform: http://btcbase.org/log/2017-11-25#1742977 << having python > 2.7 is quite like having gcc5 around.
(trilema) asciilifeform: http://btcbase.org/log/2017-11-20#1741187 << the correct solution is to not install the gcc5 nonsense to begin with, then won't need cleaning. but this won't be happening during isp winter
(trilema) asciilifeform: recall, original 'gcc5 is fatally touched' discovery happened on n00bz building rotors
(trilema) asciilifeform: gcc5 was made by wreckers.
(trilema) asciilifeform: and i mean, all of it. no gcc5 on the box anywhere.
(trilema) mike_c: that was gcc5
(trilema) mod6: mike_c: I don't think it did. I set this one up like back in the spring. And I'm fairly sure it came with gcc5 and i vanquished all the bs by hand.
(trilema) mod6: i think you can check in /etc/alternatives or whatever, to ensure there are no links or nothing to gcc5.
(trilema) mod6: are you certain that gcc5 is vanquished from your sys?
(trilema) mod6: this bug seems to pop up with gcc5 iirc.
(trilema) mod6: yeah. it doesn't work with gcc5. this looks like the ncurses bug.
(trilema) mike_c: but this did tons more. I'm going to go ahead and say gcc5 is no good for this (at least on out-of-the-box ubuntu)
(trilema) mod6: make sure to use gcc4, i've seen problems myself with gcc5
(trilema) phf: mike_c: i had it working with pretty much everything, gcc4, gcc5, clang/llvm. when i build manually i just use dependencies that whatever local package gives me, at which point make Just Works
(trilema) asciilifeform: though i will point out that gnat+gcc5/6 might not in fact suffer from same horrors as cpp on same.
(trilema) asciilifeform: incidentally for all i know gcc5ism has not even touched gnat/ada
(trilema) a111: Logged on 2017-06-06 00:42 ben_vulpes: oh christ xorg needs gcc5 now?
(trilema) asciilifeform: gcc5ification marches on.
(trilema) asciilifeform: now you might try same recipe, cum a gcc5 ban
(trilema) asciilifeform: ben_vulpes: it doesn't cure gcc5ism, no
(trilema) ben_vulpes: oh christ xorg needs gcc5 now?
(trilema) mircea_popescu: i thought this is what we're all trying. only to discover that whatever, xorg now no longer builds without gcc5 etc.
(trilema) mod6: in fact, the gcc5 thing is driving me nuts too; i've got a new notebook to replace the one with the bad 'o' key (you might remember from c3) and getting everything setup is like hair-pulling.
(trilema) asciilifeform: this is what the gcc5 folks spend their time doing.
(trilema) asciilifeform: on top of this, gcc5 happily removes , e.g., memset
(trilema) a111: Logged on 2016-09-13 17:49 asciilifeform: even gcc5 no longer does.
(trilema) asciilifeform: because cpp11 is how folx typically end up reluctantly grunting in the stake of gcc5
(trilema) asciilifeform: even gcc5 no longer does.
(trilema) asciilifeform: see also the gcc5 threads
(trilema) asciilifeform: mircea_popescu: so long as it isn't gcc5, it builds.
(trilema) asciilifeform: removing boost would be a worthy thing. BUT NOT if it multiplies the line count 2x, OR if it entails forcing gcc5 build
(trilema) asciilifeform: http://log.bitcoin-assets.com/?date=16-01-2016#1373346 << if you have a box with gcc5, just format the hdd and start over, sanely
Download hourly DB snapshot | Get Source Code