| Age | Commit message (Collapse) | Author |
|---|
|
And remove the now-invalid test for the return value of `@branchHint`.
|
|
|
|
|
|
|
|
`std.{coff,elf}`: Remove the `{MachineType,EM}.toTargetCpuArch()` functions.
|
|
I don't recall why I put these checks here -- they aren't correct. We
can freely recreate a type even if its fields have changed, because we
are going to re-do all type resolution.
The only conditions for recreations are (a) the ZIR index must not be
lost and (b) the number of captures must be the same. These conditions
are permissible because if either is violated, we can guarantee that
analysis of a valid `zirStructDecl` (etc) will never reference this
type (since the ZIR index has just been tracked, and the captures have
just been created based on the ZIR).
Adds a corresponding test case.
Resolves: #21185
|
|
These are fundamentally incapable of producing accurate information for reasons
I've laid out in #20771. Since our only use of these functions is to check that
object files have the correct machine type, and since #21020 made
`std.Target.to{Coff,Elf}Machine()` more accurate, just switch these checks over
to that and compare the machine type tags instead.
Closes #20771.
|
|
Dwarf: more cleanup
|
|
Get `mips64(el)-linux` working and start testing it
|
|
|
|
|
|
|
|
|
|
And add a corresponding test case.
|
|
|
|
|
|
|
|
These were fixed during the last few commits too. The emit_llvm_no_bin test
is renamed from the issue_12588 test.
Closes #17484
|
|
the bin
|
|
incremental: more progress
|
|
|
|
|
|
|
|
These take 3-4 minutes to run on my machine, i.e. they're not affected by the
LLVM compilation speed bug that affects mips32.
|
|
https://github.com/ziglang/zig/issues/21091
|
|
https://github.com/ziglang/zig/issues/21090
|
|
This case is adapted from #11344, and passes with `-fno-emit-bin`.
Resolves: #11344
|
|
|
|
And add a new incremental test to match!
|
|
|
|
|
|
|
|
This is in preparation for incremental and actually being able to debug
executables built by the x86_64 backend.
|
|
elf: replace .got.zig with a zig jump table
|
|
closes #72
|
|
|
|
|
|
The idea is that these tests are just too slow to include by default on a
contributor's local machine. If they want to run these, they need to opt in.
|
|
triple.
This is useful during porting work where you're not interested in running all
targets all the time while iterating on changes.
|
|
Closes #4927.
|
|
`test`: Re-enable `mips(el)-linux(-musl)` tests.
|
|
Closes #3287.
|
|
Closes #13782.
Closes #16846.
|
|
https://github.com/ziglang/zig/issues/21051
|
|
https://github.com/ziglang/zig/issues/21050
|
|
Versions can simply use the normal version range mechanism, or alternatively an
Abi tag if that makes more sense. For now, we only care about 4.5 anyway.
|
|
The type `Zcu.Decl` in the compiler is problematic: over time it has
gained many responsibilities. Every source declaration, container type,
generic instantiation, and `@extern` has a `Decl`. The functions of
these `Decl`s are in some cases entirely disjoint.
After careful analysis, I determined that the two main responsibilities
of `Decl` are as follows:
* A `Decl` acts as the "subject" of semantic analysis at comptime. A
single unit of analysis is either a runtime function body, or a
`Decl`. It registers incremental dependencies, tracks analysis errors,
etc.
* A `Decl` acts as a "global variable": a pointer to it is consistent,
and it may be lowered to a specific symbol by the codegen backend.
This commit eliminates `Decl` and introduces new types to model these
responsibilities: `Cau` (Comptime Analysis Unit) and `Nav` (Named
Addressable Value).
Every source declaration, and every container type requiring resolution
(so *not* including `opaque`), has a `Cau`. For a source declaration,
this `Cau` performs the resolution of its value. (When #131 is
implemented, it is unsolved whether type and value resolution will share
a `Cau` or have two distinct `Cau`s.) For a type, this `Cau` is the
context in which type resolution occurs.
Every non-`comptime` source declaration, every generic instantiation,
and every distinct `extern` has a `Nav`. These are sent to codegen/link:
the backends by definition do not care about `Cau`s.
This commit has some minor technically-breaking changes surrounding
`usingnamespace`. I don't think they'll impact anyone, since the changes
are fixes around semantics which were previously inconsistent (the
behavior changed depending on hashmap iteration order!).
Aside from that, this changeset has no significant user-facing changes.
Instead, it is an internal refactor which makes it easier to correctly
model the responsibilities of different objects, particularly regarding
incremental compilation. The performance impact should be negligible,
but I will take measurements before merging this work into `master`.
Co-authored-by: Jacob Young <jacobly0@users.noreply.github.com>
Co-authored-by: Jakub Konka <kubkon@jakubkonka.com>
|
|
std.debug.Dwarf: improve loading debug symbol from separate files
|
|
closes #20963
|
|
- look up the debuglink file in the directory of the executable file (instead of the cwd)
- fix parsing of debuglink section (the 4-byte alignement is within the file, unrelated to the in-memory address)
|
