00:00:08 andyf: could you give omnios a bulk build with the https://code.illumos.org/c/illumos-gate/+/2601 bits? (I'm emailing jperkin the same request, since he needs binaries) 00:00:10 → CODE REVIEW 2601: 15260 ld crashes if group members are stripped by -s (NEW) | https://www.illumos.org/issues/15260 00:48:41 richlowe: I assume jperkin will cover your request due to pkgsrc. I can build smartos-live with this if you wish. 00:51:25 Actually, fuck it, I'm doing it anyway. 00:52:19 we'll do it (smartos-)live! 00:52:20 :P 00:53:47 :P indeed. Also, I think the REAL test for me would be to update a PI with this change on it and then do a full build-strap-too build. We use platform ld for at least some of the strap build too. 00:58:52 So I'm building a PI with the change now. I have ssh+pwait combos waiting to install THAT PI onto another CN, which in turn will reboot, and which in turn will, once I'm able, to build a gcc10-primary which automatically does a strap build also. 00:59:11 * danmcd loves some pwait(1). 00:59:53 indeed 01:00:06 used that to good effect this weekend 01:02:36 gcc10...how far we've come 01:02:53 gcc 4.4.4.4lyfe 01:03:39 rzezeski: but default is still gcc7, baby!! :) :) :) 09:29:33 richlowe will do. 12:47:58 gcc10 is also in testing in OI so gcc7 is not for that long 18:20:45 rzezeski: on irc via his starlink lol 18:21:36 https://youtu.be/1kAIMlISHhU?t=26 19:16:40 gcc10 is waiting for andyf to have time, basically, as I understand it 19:22:19 I... suppose so. As far as I'm concerned, we should make the switch. It probably just needs someone to write up the proposal and get agreement. 19:30:04 I agree, for IPD purposes, probably. 19:30:09 and remember shrink to fit, you don't have to write a novel 19:30:32 obviously I'm using gcc10 almost exclusively these last few months, which doesn't exactly count, but must mean something. 19:36:02 and omnios has been on gcc10 for a good while now 19:50:15 Have we seen any Real Oddities with gcc10? 19:50:25 ISTR there were some nasty corner-cases in the 4 -> 7 jump. 19:51:00 the 4-7 stuff was mostly shrink wrapping and stuff like that 19:51:06 and some new inter-procedural crud 19:51:21 andy's testing has been, if anything, more extensive than necessary though. 19:51:33 noticing the inlining policy changes and such. 19:53:01 There has been one regression from gcc10 that I know of, which I think danmcd found, and tsoome promptly fixed (illumos 14948 fenix) 19:53:08 BUG 14948: loader: do_cpuid does corrupt memory when built with gcc 10 (Closed) 19:53:08 ↳ https://www.illumos.org/issues/14948 | https://code.illumos.org/c/illumos-gate/+/2332 19:54:18 otherwise, illumos 14421 has links to the other stuff I've found and fixed, or accepted. (fenix) 19:54:19 FEATURE 14421: use GCC 10 as default primary compiler (In Progress) 19:54:19 ↳ https://www.illumos.org/issues/14421 19:55:36 on balance, the remaining thing there (use -ftoplevel-reorder) is not something I think we should do, even though it would eliminate unused statics for us - variables too though, through constant folding, and some of those are supposed to be tuneables. 19:56:31 So close fenix illumos 14749 as will not fix? 19:56:32 FEATURE 14749: gcc10 build should use -ftoplevel-reorder (New) 19:56:33 ↳ https://www.illumos.org/issues/14749 19:57:01 yes, I'll close that one as wontfix or whatever we have 19:57:04 with some commentary 20:01:46 We've been spinning gcc10 releases (albeit DEBUG only) for some time, but not using them as much as perhaps we should. We have https://smartos.org/bugview/OS-8327 for our downstream tracking of this. 20:01:47 → OS-8327: Switch default compiler to gcc10 for SmartOS (Open) 20:13:04 Anyone familiar with AMD CPUs and fan control? The Wraith Prism fan that came with my AMD Ryzen 7 3700x CPU seems to either have failed, or just was never up to the job in the first place. 20:13:32 The fan has a 3-pin cable on it. It seems to turn on and off, but I don't think it's doing variable speed. 20:14:55 gwr: ISTR some of the AMD motherboards I've dealt with having different modes for fan control based on whether they were 4-pin ("native" PWM) or 3-pin (where they'd PWM the power line to the fan) 20:15:50 The motherboard supports 4 and 6 pin fan connectors (1:gnd, 2:pwr, 3:speed, 4:control, 5:sensor, 6:nc) 20:16:48 I'm geting frequent reports of the CPU going over 95 deg. C. Not good. 20:17:04 Is the Wraith Prism just garbage? 20:17:46 Or maybe the AsRock board is not controlling it correctly? 20:17:52 considering the boost behavior of modern chips, a better cooler probably isn't a bad investment 20:17:56 I have queries out to both outfits. :) 20:18:25 I'm remembering why we pay people to integrate systems 20:18:28 the chips will use thermal headroom you give 'em 20:20:29 Is the OS involved in controlling the CPU fan speed? 20:20:44 If so, how can I look at what it's doing, or adjust things? 20:21:24 I put a Noctua on my 3700X, gwr. 20:22:14 I did that w/o realizing the 3700x came with one. Now I think my paranoia was justified. 20:23:54 gwr: If your system has a BMC I would expect the BMC to be doing fan control 20:25:11 I would think so too. I've asked the Asrock folks about compatibility, etc. for fans. 20:26:40 danmcd: the X722 fix never got merged rifht 20:27:02 Nope. Needs LOTS of testing nobody has full cycles for. 20:27:05 just checking as i am rearraging some network things 20:27:32 (or full hardware for) 20:27:35 gwr: Can you get your IPMI sensor stuff? e.g., for an SMCI box I have: https://gist.github.com/jclulow/409f0bebb11705e1b79952f03325eb0b 20:28:41 yeah, lots of different hardware, shame it's onboard 20:34:26 yeah, the IPMI shows lots of sensor data 20:34:27 https://gist.github.com/gwr/95433268b7bb0dd4e55add2dfb8d5f36 20:36:56 I've turned it off for now (so I don't cook the thing) until I can resolve the cooling issues. 20:51:18 Well when it's on, it might help to see what it thinks the temperatures are there, and the fan RPMs 20:51:34 Hopefully the silk screens on the board match up with the IPMI labels there ... but I would not assume they do 20:53:26 rmustacc: did you have solutions for building the same tests twice on x86 (for 32bit), but not adding a whole-ass copy? 20:53:31 I ask because I think you asked me this before 20:53:37 at the very least it'd be nice to know what my answer was :) 20:59:56 An FAQ entry on the noctua.at site indocates that 3-pin fan cables are non-PWM and 4-pin fan cables are PWM. 21:00:04 that's what pmooney said earlier 21:01:05 That wasn't clear. I thought he was saying the 3-pin were controlled differently, not that they can't do variable speed. 21:02:44 https://faqs.noctua.at/support/solutions/articles/101000081757-what-pin-configuration-do-noctua-fans-use- 21:18:09 also, questions wise: people with cstyle opinions (but, please, only directly related ones). If I need to __attribute__ some stuff, and it's more stuff than usual, where would you like the line-break in the variable definition? 21:18:51 or the whole thing organized basically, I have one of everything attached to this variable, and I need to line-wrap it, and everything I do looks less good than I'd like 21:23:50 i think the 3-Pin noctua do sort of vary depending on voltage but you dont get accurate control or speed reading 21:24:29 at least the tiny 20x20x10 in my switch run slower 21:24:54 they stall on startup if it's too low though 22:52:13 richlowe: Same test source code, but build a 32-bit / 64-bit copy of it? 22:52:41 If so yeah, I do have solutions for that all over usr/src/test. 22:53:19 yeah, I took what you did, I just thought there was maybe something tidier 22:53:45 because our makefile's don't make building 32 64 together the most wholesome experience 22:53:47 but it was enough 22:54:45 dm me which version you took and I'll see if I can think of something tidier or know of which one I did?