From zoltan.somogyi at runbox.com Sat May 3 17:46:00 2025 From: zoltan.somogyi at runbox.com (Zoltan Somogyi) Date: Sat, 03 May 2025 17:46:00 +1000 (AEST) Subject: [m-rev.] for post-commit review: more specific warnings about unresolved polymorphism Message-ID: For review by anyone. Zoltan. -------------- next part -------------- A non-text attachment was scrubbed... Name: Log.urp Type: application/octet-stream Size: 1391 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DIFF.urp Type: application/octet-stream Size: 52050 bytes Desc: not available URL: From zoltan.somogyi at runbox.com Sat May 3 18:05:00 2025 From: zoltan.somogyi at runbox.com (Zoltan Somogyi) Date: Sat, 03 May 2025 18:05:00 +1000 (AEST) Subject: [m-rev.] for review: delete some redundant checks for NULL Message-ID: I asked boehm_gc's maintainer which allocating macros and functions are guaranteed never to return NULL unless the out-of-memory handler itself returns NULL, and they include all the ones we use. (I created a pull request to make this explicit in boehm_gc's upstream documentation of all the relevant macros/functions; that request was accepted.) So this diff deletes the NULL checks that we now know are redundant. For review by anyone. Since the deleted tests were extremely easy for branch predictors to handle, I don't expect a significant speedup. However, next I intend to look into optimizing away calls to MR_GC_malloc, MR_GC_malloc_atomic et al if we using boehm gc; since their bodies now contain nothing but a call to the associated boehm allocation macro, calls to them can be replaced by a direct invocation of that macro. This should yield a bigger speedup, though I don't know what it will do to code size. BTW, does anyone happen to know why *initializing* conservative gc handles both MR_BOEHM_GC and MR_HGC, but the alliocation functions themselves do not handle MR_HGC, and assume, incorrectly, that MR_CONSERVATIVE_GC can mean only MR_BOEHM_GC? Zoltan. -------------- next part -------------- A non-text attachment was scrubbed... Name: Log.null Type: application/octet-stream Size: 619 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DIFF.null Type: application/octet-stream Size: 6394 bytes Desc: not available URL: From zoltan.somogyi at runbox.com Sun May 4 04:35:41 2025 From: zoltan.somogyi at runbox.com (Zoltan Somogyi) Date: Sun, 04 May 2025 04:35:41 +1000 (AEST) Subject: [m-rev.] for post-commit review: don't warn about redundant imports when making .int files Message-ID: For review by anyone. Zoltan. -------------- next part -------------- A non-text attachment was scrubbed... Name: Log.ri Type: application/octet-stream Size: 867 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DIFF.ri Type: application/octet-stream Size: 5128 bytes Desc: not available URL: From zoltan.somogyi at runbox.com Sun May 4 11:14:30 2025 From: zoltan.somogyi at runbox.com (Zoltan Somogyi) Date: Sun, 04 May 2025 11:14:30 +1000 (AEST) Subject: [m-rev.] diff: mark_trace_goals.m Message-ID: This does not need review. Zoltan. -------------- next part -------------- A non-text attachment was scrubbed... Name: Log.mtg Type: application/octet-stream Size: 278 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DIFF.mtg Type: application/octet-stream Size: 17083 bytes Desc: not available URL: