From noreply-nasm at dev.nasm.us Sun Nov 19 08:55:17 2023 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Sun, 19 Nov 2023 16:55:17 +0000 Subject: [Nasm-bugs] [Bug 3392571] inter-section call doesn't cause error or warning In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392571 --- Comment #19 from E. C. Masloch --- By the way, since this has been added to the NASM 2.16.02 branch I have found another use for these new warnings: The eldstrict mode for my Extensions for lDebug (ELDs) requires to mark all relocations with either the reloc or reloc2 mmacros. It uses the reloc-abs warnings to flag all unmarked relocations as errors during build time. (The reloc-rel warnings are always enabled for all sources of the debugger.) This is needed because I am (mis)using NASM's multi-section -f bin output format to create the ELDs, which are "position-independent" in that an ELD's data section and code section must be loaded at a dynamically-chosen offset each. Each ELD carries a linker which runs first thing when the ELD is loaded and fixes up all the relocations. So internal relocations need to be marked by "internaldatarelocation" or "internalcoderelocation" afterwards. External relocations to the debugger host program's variables are marked by "linkdatarelocation" macros instead, and the unlinked relocations refer to "relocateddata" which is in an empty nobits section. External relocations to the debugger's functions are done using several more macros, "extcall" and "extcallcall". The eldstrict mode is mentioned on my blog: https://pushbx.org/ecm/dokuwiki/blog/pushbx/2023/1119_mid_november_work#eld_strict_mode_reloc_only_disables_reloc-abs_warnings Here's the macro file implementing the eldstrict mode: https://hg.pushbx.org/ecm/ldebug/file/0b8b44f1088a/source/eld/eldcheck.mac -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. From noreply-nasm at dev.nasm.us Thu Nov 30 05:09:19 2023 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Thu, 30 Nov 2023 13:09:19 +0000 Subject: [Nasm-bugs] [Bug 3392678] "int label" does not cause error, even for label values > 255 In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392678 E. C. Masloch changed: What |Removed |Added ---------------------------------------------------------------------------- Generated by|--- |Human Breaks existing|--- |No code| | Bug category| |Unexpected or confusing | |behavior CC| |pushbx at ulukai.org --- Comment #1 from E. C. Masloch --- I just enabled the NASM 2.16.02 reloc-abs-byte warning as an error in my macro collection: https://hg.pushbx.org/ecm/lmacros/rev/54a8c35131aa The lDebug, ldosboot boot.asm, ldosboot iniload.asm, instsect, and tsr sources all build fine with this change. I did test that eg "int cmd3" does trip the error as desired. So that works as a workaround to this issue. The new warning was added as one of a class of warnings in response to my report at https://bugzilla.nasm.us/show_bug.cgi?id=3392571 -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. From noreply-nasm at dev.nasm.us Thu Nov 30 05:12:26 2023 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Thu, 30 Nov 2023 13:12:26 +0000 Subject: [Nasm-bugs] [Bug 3392571] inter-section call doesn't cause error or warning In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392571 --- Comment #20 from E. C. Masloch --- === Quoth https://bugzilla.nasm.us/show_bug.cgi?id=3392678#c1 I just enabled the NASM 2.16.02 reloc-abs-byte warning as an error in my macro collection: https://hg.pushbx.org/ecm/lmacros/rev/54a8c35131aa The lDebug, ldosboot boot.asm, ldosboot iniload.asm, instsect, and tsr sources all build fine with this change. I did test that eg "int cmd3" does trip the error as desired. So that works as a workaround to this issue. The new warning was added as one of a class of warnings in response to my report at https://bugzilla.nasm.us/show_bug.cgi?id=3392571 -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes.