Search
Thursday, 8th of November 2018, 2:55:54 UTC
3:44:18
beach
Good morning everyone!
8:02:40
kpoeck
I now have a version of (cleavir-ir-visualizer:visualize ...) that actually displays something and opens a clouseau window
8:03:27
kpoeck
Should be Beach be online : is https://gist.github.com/kpoeck/191bb618d8ab029488f4289d14a814e3#file-cleavier-visualizer-4-png correct for:
8:04:04
kpoeck
for the hir of '(lambda(a) a)?
8:05:21
kpoeck
This is still brittle, clicking wrong - and I have to find out what is wrong - goes into an error loop and kills the process
11:14:36
beach
::notify kpoeck Looks right to me.
11:14:36
Colleen
beach: Got it. I'll let kpoeck know as soon as possible.
13:14:55
drmeister
::notify kpoeck That is fantastic!
13:14:55
Colleen
drmeister: Got it. I'll let kpoeck know as soon as possible.
13:16:02
Bike
drmeister: it said the bad thing was <badref>. dunno what that is
13:16:35
Bike
anyway, since it's quick to show up i'm going to bisect a little first
13:34:18
Bike
ok having a hard time finding an old commit that doesn't have some other problem
13:46:34
beach
kpoeck_: Looks right to me.
13:47:16
Bike
ok, '3816c16 Add llvm-sys:external-linkage argument' does build
13:53:43
Bike
the next, '5bcc6cf56 Add support for stackmaps', does not
14:05:11
drmeister
Bike: I looked at the code where I create modules and then pass them to the cmp:with-module macro (that binds cmp:*the-module*) - it all looks fine. Also - I'm able to build to my heart's content.
14:05:30
Bike
well i figured out which commit broke it.
14:05:38
Bike
looks like it's mostly c++ changes but it's a largish commit
14:06:37
drmeister
Ok - it's not reproducible - that's why I'm thinking it might be better to keep dumping the module until you find the instruction where it goes from fine to crap.
14:06:55
drmeister
But keep on keeping on.
14:08:58
Bike
i mean presumably we have different versions of a library or something
14:09:31
Bike
i'll have brew upgrade stuff
14:10:58
drmeister
Here's what I get from 'brew info llvm'
14:10:59
drmeister
https://www.irccloud.com/pastebin/T8WdDBhM/
14:11:28
drmeister
llvm: stable 7.0.0 (bottled), HEAD [keg-only] . - huh? I thought I had 6. Maybe they call 6.0.1 version 7.0
14:12:24
Bike
alright, i'll update to seven then
14:15:00
kpoeck_
I have llvm 6.01, will follow your lead once it is stable
14:15:51
drmeister
kpoeck_: We ran into a strange issue at the end of the day yesterday where llvm module's on Bike's machine are missing all of their functions. I can build the same commit perfectly fine - it's very odd.
14:16:48
kpoeck_
I think i stay with mcclim and let you do your magic :-)
14:18:54
Bike
permission denied for messing with llvm Whyyyyy
14:19:02
drmeister
https://www.reactiongifs.com/magic-3/
14:22:53
Bike
now clasp says i have the wrong llvm version
14:23:27
Bike
despite getting the same "llvm: stable 7.0.0 (bottled), HEAD [keg-only]"
14:32:47
Bike
are you not using llvm from brew?
14:37:39
Bike
it also upgraded bdw-gc and now gc/gc.h is missing
14:38:26
drmeister
I am using llvm from brew
14:38:39
Bike
why doesn't clasp complain for you, then? the wscript forces version 6
14:38:57
drmeister
But hang on - look at the output of 'brew info llvm' I pasted earlier - it is llvm 6.0
14:39:09
drmeister
https://www.irccloud.com/pastebin/T8WdDBhM/
14:39:35
drmeister
It just reports funny. First llvm: stable 7.0.0 (bottled) ... and lower down llvm/6.0.1
14:39:40
Bike
that's uh... pretty "funny"
14:39:45
Bike
i have 7.0.0 and 6.0.0 directories
14:39:56
drmeister
Ok, then you are ready for the future.
14:40:03
Bike
but not the present, i guess
14:40:08
drmeister
You have a 6.0.0 directory?
14:40:34
drmeister
I have a /usr/local/Cellar/llvm/6.0.1 directory
14:40:38
drmeister
Maybe that's the issue.
14:41:10
Bike
can we work with llvm 7 or would we need more patches
14:41:29
Bike
i don't know why the hell it's complaining about boehm now, i have two versions of boehm and both have a gc/gc.h
14:41:34
drmeister
I would need to upgrade - do you want me to give it a whirl?
14:41:53
Bike
llvm version difference seems like the most plausible culprit for the module problem
14:41:55
drmeister
Package managing is fun
14:45:09
Bike
so, yeah, versions seem like something to look at
14:45:28
Bike
maybe the include directories got fucked up somehow
14:48:02
drmeister
I'm upgrading llvm to 7 here to see what we are in for.
14:48:02
Bike
well there's no mention of gc in the -I flags, i don't know whether that's normal.
14:48:41
drmeister
You are using ./waf build_iboehm -v and don't see -lgc? I'll check...
14:49:23
Bike
not -v, it just dumps the command when the scraper fails. i'll try -v
14:49:36
Bike
the way clang (?) prints the entire file is really dumb.
14:51:00
Bike
this is the scraper command so it's the scraper scripts printing the command
14:51:11
Bike
it's not -lgc because it's not actually building, i guess
14:51:16
Bike
but there's no mention of the headers, is what i meant
14:53:25
drmeister
Does the scraping work? Are problems snowballing?
14:53:57
Bike
because it can't find the gc.h.
14:54:34
drmeister
After ./waf distclean configure ?
14:54:43
Bike
i mean, configure does find the gc library.
14:54:45
drmeister
./waf configure should report if it finds the gc library or not.
14:54:54
Bike
but clang is not getting the memo.
14:55:01
drmeister
Where is the gc.h header?
14:55:42
drmeister
I have /usr/local/Cellar/bdw-gc/7.6.8
14:55:43
Bike
/usr/local/Cellar/bdw-gc/{7.6.6,8.0.0}/include/gc/gc.h
Thursday, 8th of November 2018, 14:55:54 UTC