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] New: gcc 13 crashes with %rename in specs
Date: Mon, 26 Jun 2023 07:39:32 +0000	[thread overview]
Message-ID: <bug-110408-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110408

            Bug ID: 110408
           Summary: gcc 13 crashes with %rename in specs
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: brjd_epdjq36 at kygur dot com
  Target Milestone: ---

According to https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html 

if I apply this instruction to redefine only a part of the specs file:

%rename lib                 old_lib

*lib:
--start-group -lgcc -lc -leval1 --end-group %(old_lib)


,it is not necessary to change the whole specs file. 


Still, in gcc 13 it crashes and returns this error:

g++-13: fatal error: specs file malformed after 35 characters
compilation terminated.

35 characters is the position after the last character in the old_lib string.

I test it with an older compiler gcc 4 and it is wonderful, no error.
I suppose that this manual is not updated to work in gcc 13 and there are
changes in the syntax.

             reply	other threads:[~2023-06-26  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  7:39 brjd_epdjq36 at kygur dot com [this message]
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

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@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: 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).