From: "Michael T. Kloos" <michael@michaelkloos.com>
To: gcc@gcc.gnu.org
Subject: Bug: GCC riscv building fails at self-tests with specific march
Date: Thu, 9 Nov 2023 07:17:17 -0500 [thread overview]
Message-ID: <df275981-c465-4c60-9556-adf1c1626c8c@michaelkloos.com> (raw)
I encountered a bug when trying to build a RISC-V GCC cross-compiler. I
believe that the most relevant configure options that I used are:
--disable-multilib --with-arch=rv32ia --with-abi=ilp32 However, I can
post a full list if needed. I have the GCC git tree located at the path
"/home/quantum/devel/git/gcc" and am building it inside the
sub-directory "build1". It seems to fail when attempting to build the
self-tests. Here is an excerpt from the build output:
/home/quantum/devel/git/gcc/build1/./gcc/xgcc
-B/home/quantum/devel/git/gcc/build1/./gcc/ -xc -nostdinc /dev/null -S
-o /dev/null -fself-test=.././../gcc/testsuite/selftests
/home/quantum/devel/git/gcc/build1/./gcc/xgcc
-B/home/quantum/devel/git/gcc/build1/./gcc/ -xc++ -nostdinc /dev/null
-S -o /dev/null -fself-test=.././../gcc/testsuite/selftests cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension cc1plus: error:
'-mdiv' requires '-march' to subsume the 'M' extension It seems to be
trying to build test suites that are in conflict with my march settings.
Interestingly, I didn't have this issue when trying to build the release
version tagged "releases/gcc-13.2.0". However, I wanted to use some
newer features that were only merged less than a month ago. I tried to
build the GIT tree and encountered this error. I attempted to bisect
the issue and found that it only happens when gcc/DEV-PHASE is set to:
experimental I'm not very familar with GCC's build system, but this
suggests to me that the tests are only conditionally built on
experimental/development codebase snapshots. Michael T. Kloos
next reply other threads:[~2023-11-09 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 12:17 Michael T. Kloos [this message]
[not found] ` <9bc65a04-8a92-4c68-9fbe-c669aac38fa9@michaelkloos.com>
2023-11-09 12:30 ` Michael T. Kloos
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=df275981-c465-4c60-9556-adf1c1626c8c@michaelkloos.com \
--to=michael@michaelkloos.com \
--cc=gcc@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).