179 entries in 0.824s
ben_vulpes: phf: also, if you'd care to share your
llvm/clang compilator i'd love to take a look
phf: adlai: clasp is a good fit for tendriling trb, if i had more time, i'd use it in a similar way to shiva. but then i'm already building trb on
llvm/clang, etc. it is anti-ba though because of pedigree and ownership problem. can use it, if you have resources to read through 5 or so 100k loc projects
ascii_butugychag: clang/
llvm is well-suited for vivisection, and gcc is, unfortunately (see old threads re: why) is not
nubbins`: phf it seems like it's still not using
llvm-clang but its own gcc-5.3
nubbins`: lrwxr-xr-x 1 root wheel 5 20 Sep 2014
llvm-gcc -> clang
nubbins`: i've tried 4.9, 5.3; mp thinks maybe you targeted
llvm?
mircea_popescu: ben_vulpes recent rms/everyone else fallout over whether
llvm is good or not and gcc should or shouyld not expose the ast
ascii_field: 'We'll try to keep this up to date. Just trying to help the CLANG/
LLVM community get onto Windows.'
phf: jurov: my impression is that linking clang produced object files against gcc objects files results in heisenbugs. making the entire source code work with
llvm is essentially going through source and fixing it to conform to clang's expectations.
phf: jurov: making
llvm eat the whole is a better way to preserve sanity, because then you're dealing with fixing source, rather then hunting down opaque binary issues.
jurov: phf i did not even try
llvm to eat it whole. first i wanted to try compile eulora into dynamic lib with gcc and link that one to interpreter
jurov: asciilifeform: no, they rebuilt it with
llvm punkman:
llvm wasn't written by 15 y olds
assbot: Logged on 10-02-2015 22:07:54; asciilifeform: mircea_popescu: the
llvm thing, prior to career as apple crud, had a previous life as a darling plaything of u.s. 'comp sci' academitardia
assbot: Logged on 15-02-2015 21:43:42; asciilifeform: 'but Richard is seemingly frightened about the compiler competition from
LLVM that is out under a permissive free software license.' << fud artist lies through his teeth. rms is not 'frightened of competition under permissive licenses', but is pointing out that organized attack by shitgnomes flying (as always) flags of convenience, is under way.
mircea_popescu: or to quote the webexperts in derpxertises, "The elephant in the room is that GCC and emacs aren't competing against proprietary compilers so much as they are against
LLVM and clang. Whichever one has better features and support for programming is going to win mindshare and without mindshare you are dead. This is compounded by the fact that there are several major corporations helping
LLVM along so you need steady cont
phf: homebrew on the other hand can be told "this thing doesn't build with GCC/
llvm/clang such and such" but can't be told explicitly "build with this compiler", because!
phf: xcode comes with clang/
llvm and a bogus
llvm-gcc, which pretends to be gcc, except fails on all kinds of obscure flags, and certainly doesn't respect gcc semantics
nubbins`: and then i found myself installing
llvm trinque: in fact I built
llvm and clang earlier today
trinque cooks his balls recompiling
llvm assbot: Logged on 02-07-2015 00:17:31; phf: all patches except reward overflow, cuminer snip and igprof, up to eatblock. mac os 10.8, built dynamically with
llvm's c and cmake. synced about 5 days ago
phf: all patches except reward overflow, cuminer snip and igprof, up to eatblock. mac os 10.8, built dynamically with
llvm's c and cmake. synced about 5 days ago
☟︎ trinque: I've looked around for a common lisp on
llvm, as that's what farts into webasm
assbot: Logged on 30-08-2014 03:37:06; decimation: "The existence of
LLVM is a terrible setback for our community precisely because it is not copylefted and can be used as the basis for nonfree compilers — so that all contribution to
LLVM directly helps proprietary software as much as it helps us.'"
BingoBoingo: TomServo: asciilifeform was a FreeBSD man, but device drivers pushed him away, if I recall correctly nao CLANG+
LLVM keeps him away
BingoBoingo: <mircea_popescu> asciilifeform "compiler technology has advanced significantly in ways that GCC is not well positioned to exploit. " any clue what this specifically means ? << Probably FreeBSD 10 generally slower than 9 because clang/
LLVM thestringpuller: Apple
LLVM version 6.0 (clang-600.0.56) (based on
LLVM 3.5svn)
davout: thestringpuller: s/gcc/
llvm/
mircea_popescu:
llvm compiles faster, sucks at encryption (lol) and by degrees at everything else.
mircea_popescu: i have not looked at the matter in at least 3 years. does
llvm still own gcc much to everyone's chagrin and denial ?
mats: id like to see gcc contribs move over to
llvm, if for no other reason than to motivate both parties
decimation: "The existence of
LLVM is a terrible setback for our community precisely because it is not copylefted and can be used as the basis for nonfree compilers — so that all contribution to
LLVM directly helps proprietary software as much as it helps us.'"
☟︎ decimation: asciilifeform: I thought apple was trying to get on board with
LLVM nubbins`: thank fuck for macports, i wouldn't have gotten anywhere with apple's fork of
LLVM nubbins`: ran into the same issues as before, likely related to apple's bundling their own fork of
LLVM nubbins`: pankkake, osx does use
llvm-gcc
ozbot: FSF's Richard Stallman Calls
LLVM a 'Terrible Setback' - Slashdot
nubbins`: oh maybe. osx uses
llvm-gcc, which caused some issues
nubbins`: apparently it's some sort of weird gcc/
llvm hybrid
Diablo-D3: sun's jvm still doesnt use
llvm as the backend