From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by sourceware.org (Postfix) with ESMTPS id F025B386F032 for ; Tue, 12 Jan 2021 22:45:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org F025B386F032 Received: by mail-lf1-x12b.google.com with SMTP id s26so5791327lfc.8 for ; Tue, 12 Jan 2021 14:45:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5r2+SaW8UwzCrxKrX6Jko3X+VGUr9DnuJ4lazLhZ4bI=; b=GqNmZT2fGLj5YwL2uyLcV//lDZZaX1r/Ci/6G0sAKVg+q0+a35cuMzCtYFlktX/ZQg YN6OKZrgT5MPyGrKwjVxZ/sp0Jkv5LqBXjlhU24s3edl7coELbjIVKScxvhPq8ge0Tsv 0g8eSMCVy7aoAev579MGm3D80MXFiBVAuYlZb8yutd9I0+H0MefAkuasrth8sfd/mvxo iqi/gJDSGflQeojlUiGkjPsXA4oy4+t/mlXnLXDJJJkuiBORdpJ03M4bXiIHmMCAixu+ ujV+YoD+mG5k4OkPKDRH0GOxuklaQv7Z04lCP9y+aSjk5BRFEkj+Zcdp9W19BSHyCHJj /rIg== X-Gm-Message-State: AOAM5339y/VMYUaZRu0xVco+myQ6f3QD73KajGyDdASBUKyNycdO/VCM XSjF0+fzTPMgivAtuKn7jS4sO/xN911ooWJcTGlO3UJ4omc= X-Google-Smtp-Source: ABdhPJw9mdfhReUnaCPx1UeEMDXzMcyI1Fs/J/QkKEO4Cxh6ZMHIcoeE/xQfRcwCe79xWk/4hbAYIt0tCJM/f+Ftndg= X-Received: by 2002:a19:10:: with SMTP id 16mr457973lfa.334.1610491526280; Tue, 12 Jan 2021 14:45:26 -0800 (PST) MIME-Version: 1.0 From: squirvel voxbox Date: Tue, 12 Jan 2021 17:45:13 -0500 Message-ID: Subject: Defining a Super Specific uArch To: crossgcc@sourceware.org X-Spam-Status: No, score=-1.5 required=5.0 tests=AC_DIV_BONANZA, BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: crossgcc@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: crossgcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2021 22:45:30 -0000 Hi All, I asked a fairly similar question over on the irc channel, and didn't get a response, so I'm trying here. Let's say I'm attempting to target a super specific CPU, (in this case a RK3328, which is a 64bit armv8-a+crypto cpu). What would be the proper way to define the cpu? I am currently defining: target architecture: arm suffix to the arch-part: v8-a+crypto (according to gcc, the dash is required to define v8-a) emit assembly for CPU: cortex-a53 other items are set based on the sample aarch64-rpi3 configuration But ct-ng build fails due to: "Invalid configuration `aarch64v8-a+crypto-RK3328-linux-gnu': more than four components" (so more than 4 dashes according to the script source code) or if I disable the vendor string (set to RK3328) "Invalid configuration `aarch64v8-a+crypto-linux-gnu': machine `aarch64v8-a+crypto' not recognized" In theory I could just add all the specific uarch flags to CFLAGS/LDFLAGS such as -march=, but that feels rather hacky especially since there is an arch suffix field. Is the hacky way the way I should be defining this cpu, or am I just specifying this incorrectly? If the latter, what is the proper way to specify a super specific uarch? Thanks, squirvel