06:39:55 sommerfeld, jbk, tsoome, jclulow: thank you very much for the advice 06:40:54 I will re-design the appliance and its performance base line, thank you very much 06:55:57 yw:) 14:44:00 Is there any reason to use isnand() or isnanf() rather than the generic isnan()? 14:45:17 This is for applications (I was wondering why it had to #include ) 15:14:00 I think, you get the answer from looking the code:) 15:38:29 but I guess, there are always some historical reasons:) 15:42:12 Yes, it's the history part that I suspect is the issue. In that the history involves Studio compilers on antique Solaris versions... 18:40:14 I don't think there is history and studio. I think isnan is just c99 18:40:42 either way, it's a compiler builtin to do the magic, there's no promotion risks or anything. 18:52:10 out of curiosity, are there any amd ryzen-suporting MBs that are known to be problematic running illumos? or are they generally fine? 19:21:52 I have a question with fenix IPD 14 ramifications. 19:21:52 IPD 14: illumos and Y2038 (predraft) 19:21:53 ↳ https://github.com/illumos/ipd/tree/master/ipd/0014/README.md 19:22:54 Let's say I want to 64-bit an application that hasn't been yet. Do I install it alongside its 32-bit sibling and use isaexec? Or, assuming it's properly tested, etc, etc, do I have its usr/src/cmd/TOOL directory Makefile just compile the 64-bit version in place? 19:23:19 Asking for zoneadmd, which in SmartOS compiles BOTH today, but only ships 64-bit, and does isaexec things. I'm thinking: 19:24:02 1.) illumos-joyent zoneadmd should get rid of i386/ and amd64/ subdirs and just compile 64-bit straight into /usr/lib/zones/zoneadmd again, instead of having isaexec there. 19:25:09 2.) Since ours (which admittedly is a lot different from upstream, but still...) has been running 64-bit for quite some time, maybe -gate's can also? 19:25:55 Also, since I don't have Oracle Solaris handy, @alanc may be instructive about what Oracle did when moving away from 32-bit apps. 19:28:22 I think I would just ship the 64-bit binary, and avoid isaexec 19:29:25 I think that's what happened with the zpool and zfs commands, for instance 19:29:39 In Tribblix I'm almost at the point where isaexec becomes unused 19:31:51 We have been removing isaexec consumers, because they have no purpose 19:32:12 I don't remember how many I left, but it's very few 19:32:21 don't add more, all they do is cause one extra exec 19:32:41 unless you have an LP128 CPU you care about 19:37:19 I think we just have adb/mdb, where you have to ship both and it reexecs depending on whether the target is 32 or 64 bit 19:37:39 And in.iked, but that's it 19:40:13 Looking at an S11.4 box, it does have isaexec, but its link count is 1 19:42:02 iked I can't fix because of how closed-bins 19:42:19 we have other things that re-exec, but not via isaexec 19:43:19 ptribble: I'm sure they still have platexec too :) 19:43:25 (so do we, for that matter) 19:46:22 Hm, no such file as /usr/lib/platexec, and `pkg search platexec` comes up empty 19:47:10 Yeah, I "fix" iked when I mangle IPS to SVR4 packages 19:49:28 I fixed it in my "ship closed-bins in src with makefiles" wad 19:49:52 alanc: when did y'all EOF platexec? :) 20:02:02 hrm.. is there a way in dtrace to convert a clock_t value to (milli/micro/nano)secs ? 20:29:33 @ptribble Might we be able to fix in.iked using stupid packaging tricks? I'd like to think so but I am naive about these things sometimes. 20:31:08 You can, but it's not worth it 20:31:17 the challenge is making protocmp happy 20:31:43 not worth it to save one exec per instance running a closed daemon 20:34:37 @jbk if dtrace can access `hz` I expect it could? 20:35:17 mdb -ke "hz/D" 20:35:49 after the gitignore thing, I removed my setting to not list untracked files 20:36:02 I've caught a couple of missing, but now I have a weird one. 20:36:53 have any of you seen ttydefs.cleanup linger untracked, or is it only during a build it happens, or? 20:37:19 anyway, I'd be interested if anyone else sees it 21:06:45 sigh, annoying mis merge on my part :\ 21:13:34 richlowe: amazing, a new thing I've never heard of: platexec: not implemented on i86pc 21:14:40 jbk, danmcd: pfexec dtrace -qn 'BEGIN { trace(`hz); exit(0); }' --> 1000 21:41:18 danmcd: we mostly did in-place replacements of 32-bit programs with 64-bit ones, unless there were special issues like a public loadable module interface, but we were also doing that in the Solaris 12/11.4 development branch, so had many biweekly builds of testing before shipping as production-ready 21:42:24 richlowe: we removed platexec in 11.4 GA 21:43:39 which was the first release where we only supported sun4v and not sun4u 21:51:13 rip