From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F3BB73854810; Mon, 21 Dec 2020 16:09:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F3BB73854810 From: "jiawei at iscas dot ac.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97417] RISC-V Unnecessary andi instruction when loading volatile bool Date: Mon, 21 Dec 2020 16:09:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 10.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: jiawei at iscas dot ac.cn X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2020 16:09:49 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97417 --- Comment #56 from jiawei --- Hi Kito, I test the performance data on qemu-riscv64, and compile the benchmark with riscv-unknown-linux-gnu-gcc -Os. All the modify is set in /coremark-pro/util/make/ to change the toolchain and run env. I am also insterested about which part has changed due to the patch. I will try to find out the different.=E5=9C=A8 2020=E5=B9=B412=E6=9C=8821= =E6=97=A5 =E4=B8=8B=E5=8D=8811:38=EF=BC=8C"kito at gcc dot gnu.org" =E5=86=99=E9=81=93=EF=BC=9A https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97417 --- Comment #55 from Kito Cheng --- Hi jiawei: Thanks for the data, the performance changing for coremark-pro seems interesting, could you find which part generate different code after the patch? And I am curious what the platform you used for the performance data? -- You are receiving this mail because: You are on the CC list for the bug. 1. http://gnu.org=