-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nasm: updated to 2.16.03 #145
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
C.1.1 Version 2.16.03 This is a source build machinery and documentation update only. There are no functionality changes. Fix building from git in a separate directory from the source. Remove some irrelevant files from the source distribution. Make the documentation stronger that -O0 or -O1 are probably not what the user wants. See section 2.1.24. Fix configure --enable-lto build option. Update the included RPM .spec file. C.1.2 Version 2.16.02 Fix building from the source distribution in a separate directory from the source. Fix a number of issues when building from source, mostly involving configure or dependency generation. In particular, more aggressively avoid cross-compilation problems on Unix/Linux systems automatically invoking WINE. We could end up invoking WINE even when we didn't want to, making configure think it was running native when in fact cross-compiling. Hopefully fix compiling with the latest versions of MSVC/nmake. Windows host: add embedded manifest file. Without a manifest, Windows applications force a fixed PATH_MAX limit to any pathname; this is unnecessary. Add support VEX-encoded SM4-NI instructions. Add support for VEX-encoded SM3-NI instructions. Add support for VEX-encoded SHA512-NI instructions. PTWRITE opcode corrected (F3 prefix required.) Disassembler: the SMAP instructions are NP; notably the prefixed versions of CLAC are ERETU/ERETS. Add support for Flexible Return and Exception Delivery (FRED): the LKGS, ERETS and ERETU instructions. Fix external references to segments in the obj (OMF) and possibly other output formats. Always support up to 8 characters, i.e. 64 bits, in a string-to-numeric conversion. Preprocessor: add %map() function to expand a macro from a list of arguments, see section 4.4.7. Preprocessor: allow the user to specify the desired radix for an evaluated parameter. It doesn't make any direct difference, but can be nice for debugging or turning into strings. See the = modifier in section 4.2.1. Update documentation: __USE_package__ is now __?USE_package?__. Documentation: correct a minor problem in the expression grammar for Dx statements, see section 3.2.1. Preprocessor: correctly handle empty %rep blocks. Preprocessor: add options for a base prefix to %num(), see section 4.4.8. Preprocessor: add a %hex() function, equivalent to %eval() except that it producess hexadecimal values that are nevertheless valid NASM numeric constants, see section 4.4.5. Preprocessor: fix the parameter number in error messages (should be 1-based, like %num references to multi-line macro arguments.) Documentation: be more clear than the bin format is simply a linker built into NASM. See section 8.1. Adjust the LOCK prefix warning for XCHG. LOCK XCHG reg,mem would issue a warning for being unlockable, which is incorrect. In this case the reg,mem encoding is simply an alias for the mem,reg encoding. However, XCHG is always locked, so create a new warning (-w+prefix-lock-xchg) to explicitly flag a user-specified LOCK XCHG; default off. Future versions of NASM may remove the LOCK prefix when optimization is enabled. Fix broken dependency-list generation. Add optional warnings for specific relocation types (-w+reloc-*, see appendix A), default off. Some target environments may have specific restrictions on what kinds of relocations are possible or allowed. Error out on certain bad syntax in Dx statements, such as db 1 2. See section 3.2.1.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Sep 19, 2024
This is a point release intended to clear up a couple of CVEs and apply point fixes that have been accumulating since 5.2.1 There are a few unresolved (but minor) memory leaks related to design issues in the API that still need to be resolved. Expect those fixes in the next release. Code Fixes ---------- * Fixes for CVE-2023-48161, CVE-2022-28506, * Address SF issue #138 Documentation for obsolete utilities still installed * Address SF issue #139: Typo in "LZW image data" page ("110_2 = 4_10") * Address SF issue #140: Typo in "LZW image data" page ("LWZ") * Address SF issue #141: Typo in "Bits and bytes" page ("filed") * Note as already fixed SF issue #143: cannot compile under mingw * Address SF issue #144: giflib-5.2.1 cannot be build on windows and other platforms using c89 * Address SF issue #145: Remove manual pages installation for binaries that are not installed too * Address SF issue #146: [PATCH] Limit installed man pages to binaries, move giflib to section 7 * Address SF issue #147 [PATCH] Fixes to doc/whatsinagif/ content * Address SF issue #148: heap Out of Bound Read in gif2rgb.c:298 DumpScreen2RGB * Declared no-info on SF issue #150: There is a denial of service vulnerability in GIFLIB 5.2.1 * Declared Won't-fix on SF issue 149: Out of source builds no longer possible * Address SF issue #151: A heap-buffer-overflow in gif2rgb.c:294:45 * Address SF issue #152: Fix some typos on the html documentation and man pages * Address SF issue #153: Fix segmentation faults due to non correct checking for args * Address SF issue #154: Recover the giffilter manual page * Address SF issue #155: Add gifsponge docs * Address SF issue #157: An OutofMemory-Exception or Memory Leak in gif2rgb * Address SF issue #158: There is a null pointer problem in gif2rgb * Address SF issue #159 A heap-buffer-overflow in GIFLIB5.2.1 DumpScreen2RGB() in gif2rgb.c:298:45 * Address SF issue #163: detected memory leaks in openbsd_reallocarray giflib/openbsd-reallocarray.c * Address SF issue #164: detected memory leaks in GifMakeMapObject giflib/gifalloc.c * Address SF issue #166: a read zero page leads segment fault in getarg.c and memory leaks in gif2rgb.c and gifmalloc.c * Address SF issue #167: Heap-Buffer Overflow during Image Saving in DumpScreen2RGB Function at Line 321 of gif2rgb.c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
C.1.1 Version 2.16.03
This is a source build machinery and documentation update only. There are no functionality changes.
C.1.2 Version 2.16.02