public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-9144] RISC-V: Point our Python scripts at python3 Date: Fri, 23 Feb 2024 04:36:24 +0000 (GMT) [thread overview] Message-ID: <20240223043624.C08F1385840C@sourceware.org> (raw) https://gcc.gnu.org/g:23f5da91ccb4927562ea4d1c245639bfd4a0088b commit r14-9144-g23f5da91ccb4927562ea4d1c245639bfd4a0088b Author: Palmer Dabbelt <palmer@rivosinc.com> Date: Fri Feb 9 08:53:24 2024 -0800 RISC-V: Point our Python scripts at python3 This builds for me, and I frequently have python-is-python3 type packages installed so I think I've been implicitly testing it for a while. Looks like Kito's tested similar configurations, and the bugzilla indicates we should be moving over. gcc/ChangeLog: PR other/109668 * config/riscv/arch-canonicalize: Move to python3 * config/riscv/multilib-generator: Likewise Diff: --- gcc/config/riscv/arch-canonicalize | 2 +- gcc/config/riscv/multilib-generator | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/config/riscv/arch-canonicalize b/gcc/config/riscv/arch-canonicalize index 629bed853471..8f7d040cdeb9 100755 --- a/gcc/config/riscv/arch-canonicalize +++ b/gcc/config/riscv/arch-canonicalize @@ -1,4 +1,4 @@ -#!/usr/bin/env python +#!/usr/bin/env python3 # Tool for canonical RISC-V architecture string. # Copyright (C) 2011-2024 Free Software Foundation, Inc. diff --git a/gcc/config/riscv/multilib-generator b/gcc/config/riscv/multilib-generator index 1a957878d0cb..25cb6762ea73 100755 --- a/gcc/config/riscv/multilib-generator +++ b/gcc/config/riscv/multilib-generator @@ -1,4 +1,4 @@ -#!/usr/bin/env python +#!/usr/bin/env python3 # RISC-V multilib list generator. # Copyright (C) 2011-2024 Free Software Foundation, Inc.
reply other threads:[~2024-02-23 4:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240223043624.C08F1385840C@sourceware.org \ --to=kito@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).