…mination

Signed-off-by: deadprogram <ron@hybridgroup.com>

Signed-off-by: deadprogram <ron@hybridgroup.com>

This allows archive/tar to build and pass.

This allows archive/tar to build (but not yet pass).

Signed-off-by: deadprogram <ron@hybridgroup.com>

Signed-off-by: deadprogram <ron@hybridgroup.com>

Signed-off-by: deadprogram <ron@hybridgroup.com>

This test only applies when using the built-in LLVM version. This way,
we have a stable LLVM version to test against. Distribution versions of
LLVM (especially Debian) tend to be patched in a way that affect the
results.

Without this, pointers wouldn't be set to nil.  Add some tests.

Co-authored-by: Ayke <aykevanlaethem@gmail.com>

    // Name returns the type's name within its package for a defined type.
    // For other (non-defined) types it returns the empty string.

Signed-off-by: deadprogram <ron@hybridgroup.com>

…evice/gba

Signed-off-by: deadprogram <ron@hybridgroup.com>

Also, rename most of the SSA values while we're at it.

Signed-off-by: deadprogram <ron@hybridgroup.com>

Previously we only supported recursive types in structs. But there can
be other kinds of recursive types, like slices:

    type RecursiveSlice []RecursiveSlice

This doesn't involve structs, so it led to infinite recursion in the
compiler. This fix avoids recursion at the proper level: at the place
where the named type is defined.

Signed-off-by: deadprogram <ron@hybridgroup.com>

Adding tinygo-org#3534 by hand to avoid conflicts when I rebase.

…empty structs

It is possible to create function-local named types:

    func foo() any {
        type named int
        return named(0)
    }

This patch makes sure they don't alias with named types declared at the
package scope.

Bug originally found by Damian Gryski while working on reflect support.

There was a very subtle bug in the ADC read code: it stores a pointer to
a variable in a register, waits for the hardware to complete the read,
and then reads the value again from the local variable. Unfortunately,
the compiler doesn't know there is some form of synchronization
happening in between.

This can be fixed in roughly two ways:
  * Introduce some sort of synchronization.
  * Do a volatile read from the variable.

I chose the second one as it is probably the least intrusive. We
certainly don't need atomic instructions (the chip is single threaded),
we just need to tell the compiler the value could have changed by making
the read volatile.

This gives a small improvement now, and is needed to be able to use the
Heap2Stack transform that's available in the Attributor pass. This
Heap2Stack transform could replace our custom OptimizeAllocs pass.

Most of the changes are just IR that changed, the actual change is
relatively small.

To give an example of why this is useful, here is the code size before
this change:

    $ tinygo build -o test -size=short ./testdata/stdlib.go
       code    data     bss |   flash     ram
      95620    1812     968 |   97432    2780

    $ tinygo build -o test -size=short ./testdata/stdlib.go
       code    data     bss |   flash     ram
      95380    1812     968 |   97192    2780

That's a 0.25% reduction. Not a whole lot, but nice for such a small
patch.

…ame, and product name

Signed-off-by: deadprogram <ron@hybridgroup.com>

… USB VID, PID, manufacturer name, and product name

Signed-off-by: deadprogram <ron@hybridgroup.com>

It is implemented upstream and looks pretty stable.