terraform-provider-local: Define TERRAFORM_PROVIDER_LEGACY_INSTALL
It is present as net/terraform-provider-local and this package is
intended to replace it.
[clang-tidy] Nominate myself as a maintainer (#183173)
For the past ~8 months, I've been regularly working on clang-tidy, doing
features and cleanups, fixing issues, and reviewing PRs. I'm passionate
about the project, and I'd like to step up to be a maintainer for it!
[clang][analyzer] Add taintedness to argv (#178054)
If the execution environment is untrusted, we assume that the argv, argc
and envp parameters of the main function are attacker controlled values
and set them as taint analysis sources.
[llvm][DebugInfo] Emit DW_LNAME_Assembly for DWARFv6 assembly CUs (#183897)
Use the new DWARFv6 language code for assembly CUs. While we have a
`DW_LANG_Assembly` pre-DWARFv6 I kept the `DW_LANG_Mips_Assembler`
pre-DWARFv6 for now (I added a FIXME if we want to address it).
www/py-yt-dlp-ejs: mark as IGNORE
You cannot repack your distfile in do-fetch.
If you need to extract things and move things around, do it in
post-extract.
With hat: portmgr
ports-mgmt/pkg: update to 2.6.0
Major Changes
* create: use -t to specify the timestamp for the manifest file.
* fetch: add -s/--sumlink option for mirror mode
* triggers: only defer triggers when the need to execute an external program
* db: enable WAL mode for local databases
* query: add support for query evaluation of complex attributes
* libpkg: store ignored shlibs in manifest and db
* libpkg: respect ignred shlibs for BACKUP_LIBRARIES
* drastically reduce memory usage for all operations
* fix reproducible build issue
* autoremove: fix deletion order
* lots of documentation updates
Other Changes
* use C23 __has_include to reduce configure checks
[5 lines not shown]
[AMDGPU] Extend DS loop wait optimization with flush point tracking (#175658)
Add support for prefetch patterns where some DS loads are used in the
same iteration (creating flush points) while others remain unflushed at
the backedge.
This complements the existing pure prefetch optimization (PR172728) by
handling cases where partial same-iteration consumption occurs.
Assisted-by: Cursor / claude-4.5-opus-high
czkawka: drop maintainer.
I only rarely use this and I have really no interest in the additions that
make recent releases insanely big. Hence no update.
[lldb][Target] Allow eLanguageTypeAssembly to use ScratchTypeSystemClang (#183771)
After cleaning up some of our `LanguageType`/`SourceLangage`
round-tripping (see `7f51a2a47d2e706d04855b0e41690ebafa2b3238`), a CU
with `DW_LANG_MIPS_Assembler` will get a language type of
`eLanguageTypeAssembly` (as opposed to `eLanguageTypeMipsAssembler`).
Reason being that there is no `DW_LNAME_` (DWARFv6 language code) for
`MIPS Assembler`, only for generic `Assembly`. So it's not possible to
round-trip cleanly between pre-DWARFv6 and DWARFv6 language codes, which
LLDB relies on for storing language types (and will lean into more
heavily in the future). This broke a special provision we have where we
allow `ScratchTypeSystemClang` to be used when evaluating expressions in
assembly CUs (i.e., CUs where the debug-info explicitly sets the
language to assembly).
If we ever want to distinguish MIPS from other Assembly, the proper way
to do so is introduce a `DW_LNAME_Mips_Assembler`. For now, this patch
adds another case for `eLanguageTypeAssembly` in
`GetScratchTypeSystemForLanguage`.
[6 lines not shown]
[LAA] Fix recordAnalysis receiving null Instruction pointer (#183512)
When a memory-reading or memory-writing instruction is not a
LoadInst/StoreInst, the dyn_cast to Ld/St returns nullptr, which is then
passed to recordAnalysis. This causes the optimization remark to fall
back to the loop header location instead of pointing at the actual
problematic instruction.
Pass &I (the actual Instruction) instead.
[clang][Modules] Handle relocated modules during implicit module builds (#181836)
* To avoid the build time overhead of checking for relocated modules,
only check it once per build session.
* Enable relocated module checks in the dependency scanner.
* Add remarks to know when this is happening with `-Rmodule-validation`
This check is necessary to be able to handle new libraries appearing in
earlier search paths. This is a valid scenario when dependency info
changes between incremental builds of the same scheme, thus new build
sessions.
It is still malformed to expect new versions of libraries to be added
within the same build session.
resolves: rdar://169174750
