0.9
- Deprecated the higher level API which handles creating an environment and
installing build dependencies. This was not very complete, and the `PyPA build
project <https://github.com/pypa/build>`_ is designed for this use case.
- New ``python_executable`` parameter for :class:`.Pep517HookCaller` to run hooks
with a different Python interpreter.
- Fix for locating the script to run in the subprocess in some scenarios.
- Fix example in README to get ``build-backend`` correctly.
- Created `documentation on Read the Docs
<https://pep517.readthedocs.io/en/latest/index.html>`__
- Various minor improvements to testing.
v1.1
----
This is release v1.1, "Fernweh".
### Changes or improvements
* Our bundled PCRE dependency has been updated to 8.44.
* The `refs/remotes/origin/HEAD` file will be created at clone time to
point to the origin's default branch.
* libgit2 now uses the `__atomic_` intrinsics instead of `__sync_`
intrinsics on supported gcc and clang versions.
* The `init.defaultBranch` setting is now respected and `master` is
no longer the hardcoded as the default branch name.
* Patch files that do not contain an `index` line can now be parsed.
* Configuration files with multi-line values can now contain quotes
split across multiple lines.
* Windows clients now attempt to use TLS1.3 when available.
* Servers that request an upgrade to a newer HTTP version are
silently ignored instead of erroneously failing.
* Users can pass `NULL` to the options argument to
`git_describe_commit`.
* Clones and fetches of very large packfiles now succeeds on 32-bit
platforms.
* Custom reference database backends can now handle the repository's
`HEAD` correctly.
* Repositories with a large number of packfiles no longer exhaust the
number of file descriptors.
* The test framework now supports TAP output when the `-t` flag is
specified.
* The test framework can now specify an exact match to a test
function using a trailing `$`.
* All checkout types support `GIT_CHECKOUT_DISABLE_PATHSPEC_MATCH`.
* `git_blame` now can ignore whitespace changes using the option
`GIT_BLAME_IGNORE_WHITESPACE`.
* Several new examples have been created, including an examples for
commit, add and push.
* Mode changes during rename are now supported in patch application.
* `git_checkout_head` now correctly removes untracked files in a
subdirectory when the `FORCE | REMOVE_UNTRACKED` options are specified.
Update Ruby on Rails 6.0 related packages to 6.0.3.4.
This is security fix for ruby-actionpack60.
## Rails 6.0.3.4 (October 07, 2020) ##
* [CVE-2020-8264] Prevent XSS in Actionable Exceptions
5.1.2 (2020-10-01)
==================
- Make sure to call each invariant only once when validating invariants.
Previously, invariants could be called multiple times because when an
invariant is defined in an interface, it's found by in all interfaces
inheriting from that interface. See `pull request 215
<https://github.com/zopefoundation/zope.interface/pull/215/>`_.
5.1.1 (2020-09-30)
==================
- Fix the method definitions of ``IAdapterRegistry.subscribe``,
``subscriptions`` and ``subscribers``. Previously, they all were
defined to accept a ``name`` keyword argument, but subscribers have
no names and the implementation of that interface did not accept
that argument. See `issue 208
<https://github.com/zopefoundation/zope.interface/issues/208>`_.
- Fix a potential reference leak in the C optimizations. Previously,
applications that dynamically created unique ``Specification``
objects (e.g., used ``@implementer`` on dynamic classes) could
notice a growth of small objects over time leading to increased
garbage collection times. See `issue 216
<https://github.com/zopefoundation/zope.interface/issues/216>`_.
.. caution::
This leak could prevent interfaces used as the bases of
other interfaces from being garbage collected. Those interfaces
will now be collected.
One way in which this would manifest was that ``weakref.ref``
objects (and things built upon them, like
``Weak[Key|Value]Dictionary``) would continue to have access to
the original object even if there were no other visible
references to Python and the original object *should* have been
collected. This could be especially problematic for the
``WeakKeyDictionary`` when combined with dynamic or local
(created in the scope of a function) interfaces, since interfaces
are hashed based just on their name and module name. See the
linked issue for an example of a resulting ``KeyError``.
Note that such potential errors are not new, they are just once
again a possibility.
Version 1.4.0 released 2020-09-03
* Fix producing non-standard JSON for Infinity, -Infinity, and NaN. This could
cause errors when encoding objects into canonical JSON that previously used to
work, but were incompatible with JSON implementations in other languages.
* Use UTF-8 to fix ASCII encoding errors when data containing Unicode was
attempted to be pretty-printed.
Some packages, for example GNU sed, still use old versions of
gettext.m4 (serial 67 or older) despite having recent releases.
These versions of gettext.m4 fail to detect gettext on musl, which
has gettext built-in to libc. While there is some logic in
gettext-lib/builtin.mk for this situation, it only covers the case
where libintl is separate from libc. To fix this, set the corresponding
configure variables when gettext is built-in to libc.
Upstream Release Notes:
1.10.15
* Fixed path repo version guessing issue
1.10.14
* Fixed version guesser to look at remote branches as well as local ones
* Fixed path repositories version guessing to handle edge cases where version is different from the VCS-guessed version
* Fixed COMPOSER env var causing issues when combined with the global command
* Fixed a few issues dealing with PHP without openssl extension (not recommended at all but sometimes needed for testing)
Features
Completion speed improvements
https://golang.org/cl/257240 eliminated some duplicate type-checking in completions (and some other features), halving latency in most cases.
Improvements to symbol rankings
From https://golang.org/cl/254037:
Downrank symbols if they are:
Unexported and outside of the workspace. Since one wouldn't jump to these symbols to e.g. view documentation, they are less relevant.
Fields and interface methods. Usually one would jump to the type name, so having fields highly ranked can be noisy.
Warnings for excluded files
You will now see diagnostics if you open a file that is excluded from the current build, likely by build tags. This should aid in understanding cases when gopls fails to work on a certain file.
Better error reporting when code lenses fail
A pop-up with an error will appear if a code lens fails to run its command.
Experimental
Multi-module workspace support
The proposal described in golang/go#32394 is partially implemented, but off by default.
Enable multi-module workspace support by adding the following to your settings:
"gopls": {
"experimentalWorkspaceModule": true,
}
With this setting, you will be able to open a directory that contains multiple modules. Most features will work across modules, but some, such as go mod tidy diagnostics, are not yet implemented.
Give this a try if you're interested in this new feature, but please note that it is still very experimental.
Fixes
Toggle GC Details on Windows
There was a bug in the new experimental GC details code lens on Windows machines (golang/go#41614). We added a work-around to fix the issue.
A list of all issues fixed can be found in the gopls/v0.5.1 milestone.
Documentation
The documentation for settings is now automatically generated so it will stay up-to-date. Documentation was also updated for working with Neovim and for working on the Go project itself.
Thank you to our contributors!
@heschik @findleyr @dandua98 @pjweinb @ainar-g
Improvements
Implemented workaround for AppleClang shadowing bug (#2030)
Implemented workaround for NVCC ICE (#2005, #2027)
Fixes
Fixed detection of std::uncaught_exceptions support under non-msvc platforms (#2021)
Fixed the experimental stdout/stderr capture under Windows (#2013)
Miscellaneous
catch_discover_tests has been improved significantly (#2023, #2039)
You can now specify which reporter should be used
You can now modify where the output will be written
WORKING_DIRECTORY setting is respected
ParseAndAddCatchTests now supports TEMPLATE_TEST_CASE macros (#2031)
Various documentation fixes and improvements (#2022, #2028, #2034)
This is now a C++ package.
Cherry-pick a patch from the unreleased HEAD of cgdb for GDB 8.3+.
Take maintainership.
cgdb-0.7.1 (08/04/2019)
* Status bar messages are now displayed properly in veritical mode.
The message is now truncated according to the status bar width instead
of the width of the terminal.
* Fix spurious error from CGDB on shutdown. You may have seen,
CGDB had unexpected results. Search the logs for more details.
In the log there was a waitpid error. CGDB was using the API wrong.
* Fix issue #161 - CGDB would lock up when doing a regex search from
the status bar if the file was just opened from the file dialog and
the search did not match any text in the file. Now the search fails
to match text as expected.
* Status bar commands and gdb console commands now both show gdb
output in the gdb window (instead of only the gdb console commands).
This fixed issue #154 on github.
* Fixed issue where typing F8 would do a 'next', 'step' and
screen refresh instead of just doing a 'next' command.
* Fix issue #139 - Show appropriate logos when color disabled
Previously, if the user had colors disabled, CGDB would still show
logos that had ansi escape color sequences in them.
* Fixed :highlight regression introduced in 0.7.0.
In 0.6.8, if the user entered a :highlight command from the CGDB
status bar, for instance:
:highlight Comment ctermfg=Blue
CGDB would updated the currently displayed source file
with the requested highlighting changes. In 0.7.0 this would not occur.
Both versions honored :highlight in the .cgdbrc file.
* Fix issue #125 - CGDB can cross compile again.
* The rust syntax highlighter is now case sensitive instead of case
insensitive.
* Fix issue #129. CGDB with old versions of ncurses (5.6 or before)
would not display colors. Now it will display colors, but will
not support ansi colors in the GDB window.
* Fix issue #137. rustlexer.lpp fails to compile with some versions
of GNU autotools.
* Fix issue #135. CGDB would "freeze" when opening the file
dialog if the number of files was very large. Updating the
gdbwire parser resolved the issue.
* Add support for readline's backward-kill-word and kill-word at gdb prompt
cgdb-0.7.0 (03/21/2017)
* Remove help2man dependency. CGDB has a good info page which
should suffice.
* The hlsearch option has been added to CGDB. This improves the
searching and displaying of searching functionality within CGDB.
By default the option is off. When enabled, and there exists a
previous search, CGDB will display the search results using
the Search highlighting group. The IncSearch highlighting group
is used to display the active search. The hlsearch option
highlights previous searches in the source window, the gdb window
when in scroll mode and the file dialog window.
* CGDB now supports showing assembly code! By default, CGDB will
display source code when it is available and assembly code
when no source code is available. The option 'set disasm'
allows you to show mixed source/assembly when both are available.
* Add support to enable/disable showing assembly code in CGDB.
The default is disabled. The 'set disasm' enables showing
mixed assembly mode by default. See the documentation for more
information.
* Add the :logo command to cgdb. This tells CGDB to display a logo
in the source window.
* Add an initial Rust syntax highlighter.
* Support vi type <digit>j and <digit>k motions. Previously only
typing j or k with out a number was supported.
* Add support for marks. m[a-z] will set a local file mark and
m[A-Z] will set a global mark. '[a-z] will jump to the
corresponding local mark and '[A-Z] will jump to the corresponding
global mark. As an added bonus '' will jump to the last jump location
and '. will jump to the last executing line.
The showmarks option was introduced to show the marks in the source
window. It defaults to true. You can disable the viewing of marks
using 'set noshowmarks'.
* Add support to enable or disable color in the source window.
The default is enabled. See the documentation for more information.
* Add support for showing colors in the debug window. If gdb or the
program being debugged output an ansi escape code representing color,
https://en.wikipedia.org/wiki/ANSI_escape_code#Colors
then CGDB will display the corresponding color instead of the escape
code. This option is configurable with the set debugwincolor option.
* Add the winminwidth option to CGDB. It controls the minimum width
that a window can be resized. It corresponds to the winminheight
option. This was introduced now that CGDB can have vertically split
windows.
* Add support for vertical or horizontal splitting of the CGDB/GDB
windows. Thanks to Daniel Cohen for the original implementation
of this idea! You can change the window orientation by using the
command 'set winsplitorientation=horizontal or vertical'.
horizontal is the default orientation. Type Ctrl-w to switch between
vertical and horizontal viewing.
* Remove the TTY mode and TTY window from CGDB. This previously allowed
you to send input to the program being debugged through the TTY
window in CGDB. It is better for the user to run their program in
one terminal and attach to it with CGDB from another terminal in
order to get terminal input and terminal output working correctly.
* Add the -w command line option to CGDB. It directs CGDB to wait
to start until either a debugger is attached to it, or until a key
is written to it's stdin. This helps simplify debugging CGDB itself.
* Added GDB scroll mode in addition to the existing GDB command mode.
To enter scroll mode, type 'page up' when in GDB mode and to exit
type 'q', 'i' or 'Enter'. In scroll mode, you can scroll through
the GDB output. You can also search the GDB output with the /, ?, n
and N keys. Marks are also supported. You can set a mark by typing
m[a-z] and you can jump to a mark by typing '[a-z]. See the
documentation for more details.
* Extended support for the G command when in CGDB mode. The new supported
syntax is [<number>]G, allowing users to jump to a specific line within
the source file, rather than just the end of the source file. This is
identical to the :<number> command.
* Added support for 'executinglinedisplay' and 'selectedlinedisplay'
configuration options. See documentation for full explanation.
This allows you to configure how CGDB displays both the currently
executing line and the currently selected line.
The default for executing line is set to longarrow.
The default for selected line is set to block.
The 'arrowstyle' option has been deprecated (but still supported)
and users should use the 'executinglinedisplay' option instead.
* CGDB now only supports ncurses. Support for curses was removed.
The curses support was previously very out of date and untested.
If curses support is needed, please let us know.
Change log:
Version 3.1.0
* Python 3.9 support, no inter-interpreter support
* Add R_INSET relation for in unordered set relationship
* Unified MorePrinter code path
* Set __qualname__ to __name__ on dynamic classes
* hp.Prod(), .byprod classifier, producer profiler
* IdentitySet.prod to print tracemalloc results
* Add .all to MorePrinter
3.0.8:
New features:
- Added `validator` parameter to `input_dialog`.
Fixes:
- Cope with stdout not having a working `fileno`.
- Handle situation when /dev/null is piped into stdin, or when stdin is closed
somehow.
- Fix for telnet/ssh server: `isatty` method was not implemented.
- Display correct error when a tuple is passed into `to_formatted_text`.
- Pass along WORD parameter in `Document._is_word_before_cursor_complete`.
Fixes some key bindings.
- Expose `ProgressBarCounter` in shortcuts module.
pkgsrc changes:
---------------
* Use release archive from Github to avoid the dependency on autotools
and to remove conflict with the tag archive potentially present in
${DISTDIR} which has the same name but a different checksum.
* Reorder variables to be compliant with pkgsrc policy described in
doc/Makefile-example.
Install the new interchangeable BLAS system created by Thomas Orgis,
currently supporting Netlib BLAS/LAPACK, OpenBLAS, cblas, lapacke, and
Apple's Accelerate.framework. This system allows the user to select any
BLAS implementation without modifying packages or using package options, by
setting PKGSRC_BLAS_TYPES in mk.conf. See mk/blas.buildlink3.mk for details.
This commit should not alter behavior of existing packages as the system
defaults to Netlib BLAS/LAPACK, which until now has been the only supported
implementation.
Details:
Add new mk/blas.buildlink3.mk for inclusion in dependent packages
Install compatible Netlib math/blas and math/lapack packages
Update math/blas and math/lapack MAINTAINER approved by adam@
OpenBLAS, cblas, and lapacke will follow in separate commits
Update direct dependents to use mk/blas.buildlink3.mk
Perform recursive revbump
Changelog:
* Allow customizing mangling of generic parameters in C (#575)
* Box<T> simplifies to T* in C (4ce324c)
* ManuallyDrop<T> and MaubeUninit<T> simplify to T in C, and are opaque in C++ (0076a17)
* C++ supports a derive-ostream annotation to derive serialization of structs, unions and enums (#582)
* Large character constants have been fixed on Windows (#586)
* Constants are now generated for typedefs, etc (#589)
* The `sort_by` configuration option has been made to work for constants (#587)
* Default sort order is source order now (sort_by = "None"), and can be changed by the above option (#587)
pkgsrc changes:
---------------
* Remove the pkgconfig file generation since the version of libusb1 cannot
be obtained by parsing LIBUSB_API_VERSION from libusb.h (e.g. FreeBSD
provides 0x01000102 for 1.0.13 and Arch provides 0x01000107 for 1.0.23).
* At least FreeBSD, Debian and Arch provides a libusb-1.0.pc file for
their native implementation. Link this file to ${BUILDLINK_DIR}.
* Add logic in mk/buildlink3 to find pkgconfig files in common pkgconfig
directories (for at least FreeBSD, Debian and Arch).
This package is no longer actively maintained upstream, and it has been
effectively forked as py-bump2version, which I just imported.
As suggested by adam@.
bump2version is a small command line tool to simplify releasing software by
updating all version strings in your source code by the correct increment. It
also creates commits and tags:
- version formats are highly configurable;
- it works without any VCS, but happily reads tag information from and writes
commits and tags to Git and Mercurial if available;
- it just handles text files, so it's not specific to any programming language.
This will replace py-bumpversion, which is no longer maintained.
Ant 1.10.9 contains a bugfixes and support for using GraalVM
JavaScript inside the script family of tasks and types..
It also addresses an insecure temporary file vulnerability
vulnerability, see the security report for details
(https://ant.apache.org/security.html)
CMake 3.18.4
* FindJNI: Add aarch64 support
* VS: Populate `std:c{11,17}` flag table entries for v142
* OBJCXX: Fix regression for compiling cpp files as objcxx
* VS: Fix regression in C# source links
* FindPython: Fix erroneous regex in ABI check
* Clang: Look for llvm-lib when using MSVC-like front-end
* FindCUDA/select_compute_arch: Add CUDA 11.1 and SM86 support
1.4.2
Fix compatibility when run with pytest pre-releases, thanks Bruno Oliveira,
Fix detection of third-party debuggers, thanks Bruno Oliveira.
1.4.1
Fix coverage compatibility which was broken by 1.4.0.
1.4.0
Better detection of when we are debugging, thanks Mattwmaster58.
Release 0.18.0:
- Fix `Worder.get_primary_at` for names that start like
keywords.
- Add guess_def_lineno() to get actual function/class
definition line number
- Fix SimilarFinder/_ASTMatcher to consider 1/0 and True/False
to be unequal
- Compatibility with Python 3.8
- Add pytest.ini to collect all tests
Release 3.16.1 (22 June 2020)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.16.1 fixes two critical bugs discovered after 3.16.0 was frozen. It also
fixes character encoding problems in the documentation HTML.
Release 3.16.0 (27 May 2020)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.16.0 is a feature release with many improvements and the usual collection of
bug fixes.
This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12. There is also preliminary
support for X86/macOS 10.13, AMD64/macOS 10.13 and nanoMIPS/Linux.
* ==================== CORE CHANGES ===================
* It is now possible to dynamically change the value of many command line
options while your program (or its children) are running under Valgrind.
To see the list of dynamically changeable options, run
"valgrind --help-dyn-options".
You can change the options from the shell by using vgdb to launch
the monitor command "v.clo <clo option>...".
The same monitor command can be used from a gdb connected
to the valgrind gdbserver.
Your program can also change the dynamically changeable options using
the client request VALGRIND_CLO_CHANGE(option).
* ================== PLATFORM CHANGES =================
* MIPS: preliminary support for nanoMIPS instruction set has been added.
* ==================== TOOL CHANGES ====================
* DHAT:
- The implicit memcpy done by each call to realloc now counts towards the
read and write counts of resized heap blocks, making those counts higher
and more accurate.
* Cachegrind:
- cg_annotate's --auto and --show-percs options now default to 'yes', because
they are usually wanted.
* Callgrind:
- callgrind_annotate's --auto and --show-percs options now default to 'yes',
because they are usually wanted.
- The command option --collect-systime has been enhanced to specify
the unit used to record the elapsed time spent during system calls.
The command option now accepts the values no|yes|msec|usec|nsec,
where yes is a synonym of msec. When giving the value nsec, the
system cpu time of system calls is also recorded.
* Memcheck:
- Several memcheck options are now dynamically changeable.
Use valgrind --help-dyn-options to list them.
- The release 3.15 introduced a backward incompatible change for
some suppression entries related to preadv and pwritev syscalls.
When reading a suppression entry using the unsupported 3.14 format,
valgrind will now produce a warning to say the suppression entry will not
work, and suggest the needed change.
- Significantly fewer false positive errors on optimised code generated by
Clang and GCC. In particular, Memcheck now deals better with the
situation where the compiler will transform C-level "A && B" into "B && A"
under certain circumstances (in which the transformation is valid).
Handling of integer equality/non-equality checks on partially defined
values is also improved on some architectures.
* exp-sgcheck:
- The exprimental Stack and Global Array Checking tool has been removed.
It only ever worked on x86 and amd64, and even on those it had a
high false positive rate and was slow. An alternative for detecting
stack and global array overruns is using the AddressSanitizer (ASAN)
facility of the GCC and Clang compilers, which require you to rebuild
your code with -fsanitize=address.
* ==================== OTHER CHANGES ====================
* New and modified GDB server monitor features:
- Option -T tells vgdb to output a timestamp in the vgdb information messages.
- The gdbserver monitor commands that require an address and an optional
length argument now accepts the alternate 'C like' syntax "address[length]".
For example, the memcheck command "monitor who_points_at 0x12345678 120"
can now also be given as "monitor who_points_at 0x12345678[120]".
Release 3.15.0 (12 April 2019)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.15.0 is a feature release with many improvements and the usual collection of
bug fixes.
This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12. There is also preliminary
support for X86/macOS 10.13 and AMD64/macOS 10.13.
* ==================== CORE CHANGES ===================
* The XTree Massif output format now makes use of the information obtained
when specifying --read-inline-info=yes.
* amd64 (x86_64): the RDRAND and F16C insn set extensions are now supported.
* ==================== TOOL CHANGES ====================
* DHAT:
- DHAT been thoroughly overhauled, improved, and given a GUI. As a result,
it has been promoted from an experimental tool to a regular tool. Run it
with --tool=dhat instead of --tool=exp-dhat.
- DHAT now prints only minimal data when the program ends, instead writing
the bulk of the profiling data to a file. As a result, the --show-top-n
and --sort-by options have been removed.
- Profile results can be viewed with the new viewer, dh_view.html. When
a run ends, a short message is printed, explaining how to view the result.
- See the documentation for more details.
* Cachegrind:
- cg_annotate has a new option, --show-percs, which prints percentages next
to all event counts.
* Callgrind:
- callgrind_annotate has a new option, --show-percs, which prints percentages
next to all event counts.
- callgrind_annotate now inserts commas in call counts, and
sort the caller/callee lists in the call tree.
* Massif:
- The default value for --read-inline-info is now "yes" on
Linux/Android/Solaris. It is still "no" on other OS.
* Memcheck:
- The option --xtree-leak=yes (to output leak result in xtree format)
automatically activates the option --show-leak-kinds=all, as xtree
visualisation tools such as kcachegrind can in any case select what kind
of leak to visualise.
- There has been further work to avoid false positives. In particular,
integer equality on partially defined inputs (C == and !=) is now handled
better.
* ==================== OTHER CHANGES ====================
* The new option --show-error-list=no|yes displays, at the end of the run, the
list of detected errors and the used suppressions. Prior to this change,
showing this information could only be done by specifying "-v -v", but that
also produced a lot of other possibly-non-useful messages. The option -s is
equivalent to --show-error-list=yes.
Release 3.14.0 (9 October 2018)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.14.0 is a feature release with many improvements and the usual collection of
bug fixes.
This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12. There is also preliminary
support for X86/macOS 10.13, AMD64/macOS 10.13.
* ==================== CORE CHANGES ===================
* The new option --keep-debuginfo=no|yes (default no) can be used to retain
debug info for unloaded code. This allows saved stack traces (e.g. for
memory leaks) to include file/line info for code that has been dlclose'd (or
similar). See the user manual for more information and known limitations.
* Ability to specify suppressions based on source file name and line number.
* Majorly overhauled register allocator. No end-user changes, but the JIT
generates code a bit more quickly now.
* ================== PLATFORM CHANGES =================
* Preliminary support for macOS 10.13 has been added.
* mips: support for MIPS32/MIPS64 Revision 6 has been added.
* mips: support for MIPS SIMD architecture (MSA) has been added.
* mips: support for MIPS N32 ABI has been added.
* s390: partial support for vector instructions (integer and string) has been
added.
* ==================== TOOL CHANGES ====================
* Helgrind: Addition of a flag
--delta-stacktrace=no|yes [yes on linux amd64/x86]
which specifies how full history stack traces should be computed.
Setting this to =yes can speed up Helgrind by 25% when using
--history-level=full.
* Memcheck: reduced false positive rate for optimised code created by Clang 6
/ LLVM 6 on x86, amd64 and arm64. In particular, Memcheck analyses code
blocks more carefully to determine where it can avoid expensive definedness
checks without loss of precision. This is controlled by the flag
--expensive-definedness-checks=no|auto|yes [auto].
* ==================== OTHER CHANGES ====================
* Valgrind is now buildable with link-time optimisation (LTO). A new
configure option --enable-lto=yes allows building Valgrind with LTO. If the
toolchain supports it, this produces a smaller/faster Valgrind (up to 10%).
Note that if you are doing Valgrind development, --enable-lto=yes massively
slows down the build process.
Version 0.7.18
~~~~~~~~~~~~~~
Released: 2020-09-07
New Features:
- Add content rating system APIs from gnome-software (Philip Withnall)
- Add "validate-version" command (Florian Müllner)
Bugfixes:
- Allow timestamp in the future in validate-relax (Bartłomiej Piotrowski)
- Don't ignore localized strings that are the same as original (Isaque Galdino)
- Fix crash with invalid children of <ul/> (Fabian Vogt)
- Lower the OARS/CSM mapping of sex-homosexuality/intense (Philip Withnall)
- Properly initialize mutexes (Laurent Bigonville)
- Test launchable tags in validation (Ian McInerney)
httplib2 for use with requests session object.
It was written because httplib2's better support for caching is often
mitigated by its lack of thread safety. The same is true of requests in
terms of caching.
