public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107042] New: GCC build error after today's change
Date: Mon, 26 Sep 2022 19:10:33 +0000 [thread overview]
Message-ID: <bug-107042-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107042
Bug ID: 107042
Summary: GCC build error after today's change
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: unlvsur at live dot com
Target Milestone: ---
g++ -no-pie -g -O2 -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common
-DHAVE_CONFIG_H -static-libstdc++ -static-libgcc gcov.o json.o \
hash-table.o ggc-none.o libcommon.a ../libcpp/libcpp.a
../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a
../libdecnumber/libdecnumber.a -L./../zlib -lz -o gcov
../../../../../gcc/gcc/gcc.cc:1262:1: error: expected ',' or ';' before
'ASM_COMPRESS_DEBUG_SPEC'
1262 | ASM_COMPRESS_DEBUG_SPEC
| ^~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2022-09-26 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 19:10 unlvsur at live dot com [this message]
2022-09-26 19:26 ` [Bug bootstrap/107042] " marxin at gcc dot gnu.org
2022-09-26 19:28 ` unlvsur at live dot com
2022-09-26 19:32 ` marxin at gcc dot gnu.org
2022-09-26 19:33 ` unlvsur at live dot com
2022-09-26 19:46 ` marxin at gcc dot gnu.org
2022-09-26 20:09 ` unlvsur at live dot com
2022-09-26 20:35 ` redi at gcc dot gnu.org
2022-09-26 20:36 ` redi at gcc dot gnu.org
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-107042-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).