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 driver/110408] [13/14 Regression] gcc 13 crashes with %rename in specs Date: Wed, 28 Jun 2023 22:18:21 +0000 [thread overview] Message-ID: <bug-110408-4-sTfQVFMfmz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110408-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110408 Brjd <brjd_epdjq36 at kygur dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Brjd <brjd_epdjq36 at kygur dot com> --- Please ignore it. I test it more and find out that it is my misunderstanding that I can make it the default specs if I use the %rename option. However, the compiler is not designed in this way. Please tell if there are other options. AFAIK currently there are two options to change the specs behavior. First, I can override only a part of the specs file with the %rename option. The shortage here is that it is not the default and I should invoke it manually every time by the -specs=/path-to-my-specs-file. The second way is a rebuild of the GCC or changes in the whole specs file. This is the way I can set the default without invoking in the command line -specs=/path-to-my-specs-file. I do the first one and that causes the error since I use the GCC without -specs. The compiler simply replaces the whole specs with my custom overriding specs and fails.
prev parent reply other threads:[~2023-06-28 22:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-26 7:39 [Bug driver/110408] New: " brjd_epdjq36 at kygur dot com 2023-06-28 13:31 ` [Bug driver/110408] " brjd_epdjq36 at kygur dot com 2023-06-28 18:27 ` [Bug driver/110408] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-28 22:18 ` 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-110408-4-sTfQVFMfmz@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).