From: Florian Weimer <fweimer@redhat.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] build-many-glibcs: Add a RISC-V config with most of the B extensions
Date: Wed, 06 Sep 2023 22:43:08 +0200 [thread overview]
Message-ID: <87pm2vxcbn.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230906150605.10221-2-palmer@rivosinc.com> (Palmer Dabbelt's message of "Wed, 6 Sep 2023 08:06:06 -0700")
* Palmer Dabbelt:
> + self.add_config(arch='riscv64',
> + os_name='linux-gnu',
> + variant='rv64imafdcb-lp64d',
> + gcc_cfg=['--with-arch=rv64imafdc_zba_zbb_zbs', '--with-abi=lp64d',
> + '--disable-multilib'])
I doubt we need a separate GCC configuration, you should be able to use
the existing compiler for that and just change the glibc build flags.
I expect we need some sort of version check because these flags are
rather recent, right? To what extend do they actually impact code
generation for glibc?
Thanks,
Florian
next prev parent reply other threads:[~2023-09-06 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 15:06 Palmer Dabbelt
2023-09-06 20:43 ` Florian Weimer [this message]
2023-09-07 15:24 ` Palmer Dabbelt
2023-09-07 15:50 ` Florian Weimer
2023-09-07 16:39 ` Palmer Dabbelt
2023-09-07 17:00 ` Evan Green
2023-09-07 17:05 ` Palmer Dabbelt
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=87pm2vxcbn.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@rivosinc.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).