public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "brjd_epdjq36 at kygur dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111570] -march=generic prints error Date: Mon, 25 Sep 2023 17:01:24 +0000 [thread overview] Message-ID: <bug-111570-4-TBqa87SRFx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111570 --- Comment #2 from Brjd <brjd_epdjq36 at kygur dot com> --- Thank you and I also read this guide. My point is that the generic arch might be possible in theory. If the gcc builds for the oldest CPU with x86_64, is it possible that code will run on all modern CPU since their subset includes also that of their predecessor. How about making it default to that generic or baseline build for that limited CPU? If I could ask you also more questions, let me ask you about this problem. The guide doesn't mention anything about the specific arch. If -march=cpu what is better -mtune=cpu where cpu is the same as in arch or -mtune=generic so that the code tunes to all CPU kinds of this family.If the tune is empty, is it default generic or native and the arch is not clear either. One question more, I am not able to find a guide about the gcc build and no information whether the gcc may be built in targets like LLVM and clang. For example, is it possible to build first only the LLVM, then stop and resume with clang etc. or first, gcc's only c modiule and its submodules, then stop and resume with its g++ module and submodules, next with libgcc, libstdc++ etc.? It would be great, especially for long bootstraps and stage 2, but I find only make all-gcc, target-libgcc which however build almost all of the compiler.
prev parent reply other threads:[~2023-09-25 17:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-24 12:03 [Bug demangler/111570] New: " brjd_epdjq36 at kygur dot com 2023-09-25 8:48 ` [Bug target/111570] " redi at gcc dot gnu.org 2023-09-25 17:01 ` brjd_epdjq36 at kygur dot com [this message]
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-111570-4-TBqa87SRFx@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: linkBe 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).