Newest at the top
| 2026-04-04 00:14:07 +0000 | absurdvoid | (~absurdvoi@user/absurdvoid) (Ping timeout: 264 seconds) |
| 2026-04-04 00:11:34 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-04-04 00:06:37 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 23:55:57 +0000 | merijn | (~merijn@62.45.136.136) (Ping timeout: 255 seconds) |
| 2026-04-03 23:50:53 +0000 | merijn | (~merijn@62.45.136.136) merijn |
| 2026-04-03 23:47:57 +0000 | <geekosaur> | "-Wall" isn't all warnings, use "-Weverything" "-Weverything isn't all warnings either, there are some that must be enabled explicitly" |
| 2026-04-03 23:43:32 +0000 | tromp | (~textual@2001:1c00:340e:2700:f5b2:b468:1c7d:8570) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2026-04-03 23:38:35 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2026-04-03 23:33:50 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 23:31:14 +0000 | <EvanR> | don't even enable it |
| 2026-04-03 23:31:08 +0000 | <EvanR> | extra warnings in another flag are secondary |
| 2026-04-03 23:30:50 +0000 | <EvanR> | it doesn't have all warnings no but someone decided it has all warnings that must be taken seriously |
| 2026-04-03 23:30:21 +0000 | <EvanR> | haha that whole issue boiled down to what -Wall means actually and culturally |
| 2026-04-03 23:29:19 +0000 | wootehfoot | (~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer) |
| 2026-04-03 23:26:54 +0000 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2026-04-03 23:24:32 +0000 | tremon | (~tremon@83.80.159.219) (Quit: getting boxed in) |
| 2026-04-03 23:20:18 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-04-03 23:17:34 +0000 | wennefer0 | (~wennefer0@user/wennefer0) (Quit: Textual IRC Client: www.textualapp.com) |
| 2026-04-03 23:15:32 +0000 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2026-04-03 23:10:21 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 23:05:00 +0000 | arandombit | (~arandombi@user/arandombit) (Ping timeout: 244 seconds) |
| 2026-04-03 22:59:21 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-04-03 22:58:45 +0000 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2026-04-03 22:54:27 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 22:44:07 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-04-03 22:38:40 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 22:37:03 +0000 | divlamir | (~divlamir@user/divlamir) divlamir |
| 2026-04-03 22:32:59 +0000 | Digitteknohippie | Digit |
| 2026-04-03 22:30:23 +0000 | divlamir_ | (~divlamir@user/divlamir) (Ping timeout: 244 seconds) |
| 2026-04-03 22:27:45 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2026-04-03 22:26:15 +0000 | divlamir | (~divlamir@user/divlamir) (Read error: Connection reset by peer) |
| 2026-04-03 22:26:05 +0000 | divlamir_ | (~divlamir@user/divlamir) divlamir |
| 2026-04-03 22:22:38 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 22:12:53 +0000 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2026-04-03 22:11:30 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-04-03 22:11:08 +0000 | emmanuelux | (~em@user/emmanuelux) emmanuelux |
| 2026-04-03 22:09:33 +0000 | machinedgod | (~machinedg@d172-219-48-230.abhsia.telus.net) machinedgod |
| 2026-04-03 22:08:59 +0000 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 265 seconds) |
| 2026-04-03 22:07:59 +0000 | Guest20 | (~Guest20@149.3.7.235) (Quit: Client closed) |
| 2026-04-03 22:06:51 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 22:05:10 +0000 | puke | (~puke@user/puke) (Ping timeout: 250 seconds) |
| 2026-04-03 21:56:07 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-04-03 21:48:49 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-03 21:47:55 +0000 | <tomsmeding> | same for clang 21.1.6 |
| 2026-04-03 21:47:07 +0000 | <tomsmeding> | monochrom: I do not share your observations, I get no -Wunused-result for read(2) whatsoever on my system (linux, gcc 15.2.1), but I do get that warning for realloc() regardless of the optimisation level |
| 2026-04-03 21:47:05 +0000 | <monochrom> | When confronted with an unused-value problem, some people go, "I know, I will store it in a fresh variable!". Now they have two problems. >:) |
| 2026-04-03 21:44:41 +0000 | <tomsmeding> | monochrom: although now you have a -Wunused-but-set-variable ;) |
| 2026-04-03 21:44:00 +0000 | <tomsmeding> | yes, I'm a little confused too |
| 2026-04-03 21:43:41 +0000 | <monochrom> | Adding "int r; r =" kills the warning under -O2. So it is not even like "we need an elaborate live-variable analysis to discover unused results" :) |
| 2026-04-03 21:37:56 +0000 | synchromesh | (~john@2406:5a00:2412:2c00:343e:4e23:bce:73a3) synchromesh |