public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineetg@rivosinc.com>
To: Thomas Schwinge <thomas.schwinge@siemens.com>,
	Kito Cheng <kito.cheng@gmail.com>,
	"Maciej W. Rozycki" <macro@embecosm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Andrew Waterman <andrew@sifive.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	patrick@rivosinc.com, jlaw@ventanamicro.com,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH] RISC-V/testsuite: Run target testing over all the usual optimization levels
Date: Thu, 25 May 2023 14:20:38 -0700	[thread overview]
Message-ID: <44506218-70bd-0b7b-a560-744bb24376a9@rivosinc.com> (raw)
In-Reply-To: <1bfe6de8-8510-4c30-7b2d-f22a599e750d@rivosinc.com>


On 5/25/23 14:17, Vineet Gupta wrote:
> FWIW if you want to test this out at your end, it is super easy.
>
> |git clone https://github.com/riscv-collab/riscv-gnu-toolchain 
> toolchain-upstream cd toolchain-upstream git submodule init git 
> submodule update ||./configure --with-arch=rv64imafdc --with-abi=lp64d 
> --enable-multilib --enable-linux --prefix=<path-to-install> make -j 
> make report-linux SIM=qemu Thx, -Vineet ||| 

Sorry the mailer clobbered the instructions.

git clone https://github.com/riscv-collab/riscv-gnu-toolchain 
toolchain-upstream
cd toolchain-upstream
git submodule init
git submodule update
./configure --with-arch=rv64imafdc --with-abi=lp64d --enable-multilib 
--enable-linux --prefix=<path-to-install>
make -j
make -j make report-linux SIM=qemu

Thx



  reply	other threads:[~2023-05-25 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 23:04 Maciej W. Rozycki
2022-02-07 16:22 ` Kito Cheng
2022-02-08 12:24   ` Maciej W. Rozycki
2023-05-25 20:56   ` Thomas Schwinge
2023-05-25 21:17     ` Vineet Gupta
2023-05-25 21:20       ` Vineet Gupta [this message]
2023-05-26  0:06       ` Vineet Gupta

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=44506218-70bd-0b7b-a560-744bb24376a9@rivosinc.com \
    --to=vineetg@rivosinc.com \
    --cc=andrew@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jlaw@ventanamicro.com \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=macro@embecosm.com \
    --cc=palmer@dabbelt.com \
    --cc=patrick@rivosinc.com \
    --cc=thomas.schwinge@siemens.com \
    /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: link
Be 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).