Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 94 for architectures (0.1 sec)

  1. src/cmd/asm/doc.go

    # Command Line
    
    Usage:
    
    	go tool asm [flags] file
    
    The specified file must be a Go assembly file.
    The same assembler is used for all target operating systems and architectures.
    The GOOS and GOARCH environment variables set the desired target.
    
    Flags:
    
    	-D name[=value]
    		Predefine symbol name with an optional simple value.
    		Can be repeated to define multiple symbols.
    	-I dir1 -I dir2
    Registered: Tue Sep 09 11:13:09 UTC 2025
    - Last Modified: Tue Aug 22 20:46:45 UTC 2023
    - 1.8K bytes
    - Viewed (0)
  2. src/buildall.bash

    # Use of this source code is governed by a BSD-style
    # license that can be found in the LICENSE file.
    
    # Usage: buildall.bash [-e] [pattern]
    #
    # buildall.bash builds the standard library for all Go-supported
    # architectures.
    #
    # Originally the Go build system used it as a smoke test to quickly
    # flag portability issues in builders named "misc-compile" or "all-compile".
    # As of CL 464955, the build system uses make.bash -compile-only instead,
    Registered: Tue Sep 09 11:13:09 UTC 2025
    - Last Modified: Tue Apr 23 17:45:23 UTC 2024
    - 2.1K bytes
    - Viewed (0)
  3. buildscripts/cross-compile.sh

    #!/bin/bash
    
    set -e
    # Enable tracing if set.
    [ -n "$BASH_XTRACEFD" ] && set -x
    
    function _init() {
    	## All binaries are static make sure to disable CGO.
    	export CGO_ENABLED=0
    
    	## List of architectures and OS to test coss compilation.
    	SUPPORTED_OSARCH="linux/ppc64le linux/mips64 linux/amd64 linux/arm64 linux/s390x darwin/arm64 darwin/amd64 freebsd/amd64 windows/amd64 linux/arm linux/386 netbsd/amd64 linux/mips openbsd/amd64 linux/riscv64"
    }
    
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Sun Jun 08 16:12:05 UTC 2025
    - 972 bytes
    - Viewed (0)
  4. CHANGELOG/CHANGELOG-1.29.md

    ### Container Images
    
    All container images are available as manifest lists and support the described
    architectures. It is also possible to pull a specific architecture directly by
    adding the "-$ARCH" suffix  to the container image name.
    
    name | architectures
    ---- | -------------
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Mar 12 00:36:01 UTC 2025
    - 429.6K bytes
    - Viewed (1)
  5. CHANGELOG/CHANGELOG-1.27.md

    ### Container Images
    
    All container images are available as manifest lists and support the described
    architectures. It is also possible to pull a specific architecture directly by
    adding the "-$ARCH" suffix  to the container image name.
    
    name | architectures
    ---- | -------------
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Jul 17 07:48:22 UTC 2024
    - 466.3K bytes
    - Viewed (2)
  6. doc/asm.html

    the offsets being used to access them are correct.
    </p>
    
    <h2 id="architectures">Architecture-specific details</h2>
    
    <p>
    It is impractical to list all the instructions and other details for each machine.
    To see what instructions are defined for a given machine, say ARM,
    look in the source for the <code>obj</code> support library for
    that architecture, located in the directory <code>src/cmd/internal/obj/arm</code>.
    Registered: Tue Sep 09 11:13:09 UTC 2025
    - Last Modified: Tue Nov 28 19:15:27 UTC 2023
    - 36.3K bytes
    - Viewed (0)
  7. CHANGELOG/CHANGELOG-1.31.md

    ### Container Images
    
    All container images are available as manifest lists and support the described
    architectures. It is also possible to pull a specific architecture directly by
    adding the "-$ARCH" suffix  to the container image name.
    
    name | architectures
    ---- | -------------
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Aug 13 19:49:57 UTC 2025
    - 429.6K bytes
    - Viewed (0)
  8. CHANGELOG/CHANGELOG-1.28.md

    ### Container Images
    
    All container images are available as manifest lists and support the described
    architectures. It is also possible to pull a specific architecture directly by
    adding the "-$ARCH" suffix  to the container image name.
    
    name | architectures
    ---- | -------------
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Oct 23 20:13:20 UTC 2024
    - 456.9K bytes
    - Viewed (1)
  9. docs/fr/docs/deployment/docker.md

    ```Dockerfile
    FROM tiangolo/uvicorn-gunicorn-fastapi:python3.7
    
    COPY ./app /app/app
    ```
    
    ### Raspberry Pi et autres architectures
    
    Si vous utilisez Docker sur un Raspberry Pi (qui a un processeur ARM) ou toute autre architecture, vous pouvez créer un `Dockerfile` à partir de zéro, basé sur une image de base Python (qui est multi-architecture) et utiliser Uvicorn seul.
    
    Dans ce cas, votre `Dockerfile` pourrait ressembler à ceci :
    
    ```Dockerfile
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sat Nov 09 16:39:20 UTC 2024
    - 7.5K bytes
    - Viewed (0)
  10. CHANGELOG/CHANGELOG-1.32.md

    ### Container Images
    
    All container images are available as manifest lists and support the described
    architectures. It is also possible to pull a specific architecture directly by
    adding the "-$ARCH" suffix  to the container image name.
    
    name | architectures
    ---- | -------------
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Aug 13 14:49:49 UTC 2025
    - 412.3K bytes
    - Viewed (0)
Back to top