public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111622] [13 Regression] EVRP compile-time hog compiling risc-v insn-opinit.cc
Date: Fri, 29 Sep 2023 06:20:19 +0000 [thread overview]
Message-ID: <bug-111622-4-bHABjNwte5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111622-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111622
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> For riscv cross compilers you need to invoke the driver since that feeds
> -mabi and -march to cc1plus required to identify the target as 64bit ...
>
> That would be -march=rv64imafdc_zicsr_zifencei -mabi=lp64d for example.
Err, forget that. The testcase is for a x86_64 compiler, but you need
-fno-exceptions -fno-rtti -O2 to reproduce the GCC case exactly (it also
works with plain -O2).
So, this is in _building_ a x86_64 -> riscv cross (not using it).
next prev parent reply other threads:[~2023-09-29 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 8:43 [Bug tree-optimization/111622] New: " rguenth at gcc dot gnu.org
2023-09-28 8:44 ` [Bug tree-optimization/111622] " rguenth at gcc dot gnu.org
2023-09-28 8:44 ` rguenth at gcc dot gnu.org
2023-09-28 8:45 ` rguenth at gcc dot gnu.org
2023-09-28 14:58 ` amacleod at redhat dot com
2023-09-29 6:17 ` rguenth at gcc dot gnu.org
2023-09-29 6:20 ` rguenth at gcc dot gnu.org [this message]
2023-10-12 16:32 ` amacleod at redhat dot com
2023-10-13 13:23 ` cvs-commit at gcc dot gnu.org
2023-10-13 13:23 ` cvs-commit at gcc dot gnu.org
2023-10-13 13:50 ` amacleod at redhat dot com
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=bug-111622-4-bHABjNwte5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).