From: unlvsur unlvsur <unlvsur@live.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>,
"jw@raven.inka.de" <jw@raven.inka.de>
Subject: Re: How to omit libc (newlib) on bare metal (freestanding)?
Date: Sat, 11 Mar 2023 22:59:47 +0000 [thread overview]
Message-ID: <BYAPR05MB4694D753713CF0419FE6ACF8D6BB9@BYAPR05MB4694.namprd05.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
"FFreestanding" doesn't imply that you should build your C or C++ program using a freestanding approach. Additionally, it's worth noting that GCC 9.3 is outdated and will soon be deprecated, so it's recommended that you upgrade to the latest native GCC version first. Then, use this new GCC version to build a new cross toolchain for the latest GCC 13 (which will soon be updated to GCC 14). It's important to keep in mind that freestanding C++ is not supported by GCC versions prior to GCC 12. To create a new cross compiler, you can use the following configure options: --without-headers --disable-shared --disable-threads --disable-nls --disable-werror --disable-libssp --disable-libquadmath --disable-libbacktarce --enable-languages=c,c++ --enable-multilib --disable-bootstrap --disable-libstdcxx-verbose --with-libstdcxx-eh-pool-obj-count=0 --disable-sjlj-exceptions --disable-hosted-libstdcxx. Once this is complete, you will have a new cross freestanding GCC toolchain that doesn't rely on newlib dependencies. Finally, you can use an x86_64-w64-mingw32 target GCC cross compiler for Canadian compilation to obtain a toolchain that runs on Windows.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
next reply other threads:[~2023-03-11 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 22:59 unlvsur unlvsur [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 23:31 Josef Wolf
2023-02-22 9:02 ` Jonathan Wakely
2023-02-22 9:03 ` Jonathan Wakely
2023-02-22 11:35 ` Richard Earnshaw
2023-03-06 14:40 ` Josef Wolf
2023-03-07 11:08 ` Arsen Arsenović
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=BYAPR05MB4694D753713CF0419FE6ACF8D6BB9@BYAPR05MB4694.namprd05.prod.outlook.com \
--to=unlvsur@live.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jw@raven.inka.de \
/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).