[OpenCL] Diagnose block references in selection operator (#114824)
In addition to the invocation case that is already diagnosed, also
diagnose when a block reference appears on either side of a ternary
selection operator.
Until now, clang would accept the added test case only to crash during
code generation.
[StrTable] Switch diag group names to `llvm::StringTable` (#123302)
Previously, they used a hand-rolled Pascal-string encoding different
from all the other string tables produced from TableGen. This moves them
to use the newly introduced runtime abstraction, and enhances that
abstraction to support iterating over the string table as used in this
case.
From what I can tell the Pascal-string encoding isn't critical here to
avoid expensive `strlen` calls, so I think this is a simpler and more
consistent model. But if folks would prefer a Pascal-string style
encoding, I can instead work to switch the `StringTable` abstraction
towards that. It would require some tricky tradeoffs though to make it
reasonably general: either using 4 bytes instead of 1 byte to encode the
size, or having a fallback to `strlen` for long strings.
py-codespell: updated to 2.4.0
2.4.0
Exclude bots from generated release notes
Refactor: Move some code to new files for reuse
Add equipmnet->equipment
Set better project description
Additional en-GB → en-US entries
Consistent error messages
Add 'driven' as 'drivin' variant
More typos
Add reusing misspelling and variants
Add typos found in Emacs and elsewhere
MAINT: Fix codecov
Add typos found in GNU Guile
Add corrections from Aspell
Add entries to dictionary_informal.txt
Add rare typo lien->line
[92 lines not shown]
py-sphinx-issues: updated to 5.0.0
5.0.0 (2024-10-11)
Remove :cwe: and :cve: roles, as these are officially included in Sphinx>=8.1.0.
Support Python 3.9-3.13. Python 3.8 is no longer supported.
[Clang] Implement P2280R4 Using unknown pointers and references in constant expressions (#95474)
P2280R4 allows the use of references in pointers of unknown origins in a
constant expression context but only in specific cases that could be
constant expressions.
We track whether a variable is a constexpr unknown in a constant
expression by setting a flag in either APValue or LValue and using this
flag to prevent using unknown values in places where it is not allowed.
Fixes: https://github.com/llvm/llvm-project/issues/63139https://github.com/llvm/llvm-project/issues/63117
py-test-httpserver: updated to 1.1.1
1.1.1
New Features
- Add a new ``expect`` method to the ``HTTPServer`` object which allows
developers to provide their own request matcher object.
py-tzdata: updated to 2025.1
Version 2025.1
Upstream version 2025a released 2025-01-15T18:47:24+00:00
Briefly:
Paraguay adopts permanent -03 starting spring 2024. Improve pre-1991 data for
the Philippines. Etc/Unknown is now reserved.
Changes to future timestamps
Paraguay will stop changing its clocks after the spring-forward transition on
2024-10-06, so it is now permanently at -03. (Thanks to Heitor David Pinto and
Even Scharning.) This affects timestamps starting 2025-03-22, as well as the
obsolescent tm_isdst flags starting 2024-10-15.
Changes to past timestamps
[19 lines not shown]
py-sqlalchemy: updated to 2.0.37
2.0.37
Released: January 9, 2025
orm
[orm] [bug]
Fixed issue regarding Union types that would be present in the registry.type_annotation_map of a registry or declarative base class, where a Mapped element that included one of the subtypes present in that Union would be matched to that entry, potentially ignoring other entries that matched exactly. The correct behavior now takes place such that an entry should only match in registry.type_annotation_map exactly, as a Union type is a self-contained type. For example, an attribute with Mapped[float] would previously match to a registry.type_annotation_map entry Union[float, Decimal]; this will no longer match and will now only match to an entry that states float. Pull request courtesy Frazer McLean.
[orm] [bug]
Fixed bug in how type unions were handled within registry.type_annotation_map as well as Mapped that made the lookup behavior of a | b different from that of Union[a, b].
[orm] [bug]
Consistently handle TypeAliasType (defined in PEP 695) obtained with the type X = int syntax introduced in python 3.12. Now in all cases one such alias must be explicitly added to the type map for it to be usable inside Mapped. This change also revises the approach added in 11305, now requiring the TypeAliasType to be added to the type map. Documentation on how unions and type alias types are handled by SQLAlchemy has been added in the Customizing the Type Map section of the documentation.
[75 lines not shown]
[lld] Migrate away from PointerUnion::dyn_cast (NFC) (#123891)
Note that PointerUnion::dyn_cast has been soft deprecated in
PointerUnion.h:
// FIXME: Replace the uses of is(), get() and dyn_cast() with
// isa<T>, cast<T> and the llvm::dyn_cast<T>
Literal migration would result in dyn_cast_if_present (see the
definition of PointerUnion::dyn_cast), but this patch uses cast
because we know expect isa<Symbol *>(rel.referent) to be true.
[AST] Migrate away from PointerUnion::dyn_cast (NFC) (#123890)
Note that PointerUnion::dyn_cast has been soft deprecated in
PointerUnion.h:
// FIXME: Replace the uses of is(), get() and dyn_cast() with
// isa<T>, cast<T> and the llvm::dyn_cast<T>
Literal migration would result in dyn_cast_if_present (see the
definition of PointerUnion::dyn_cast), but this patch uses dyn_cast
because we expect TemplateOrSpecialization to be nonnull.
