public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pkubaj at anongoth dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/89494] Bootstrap error when using GCC 4.2.1
Date: Wed, 24 Mar 2021 20:55:33 +0000 [thread overview]
Message-ID: <bug-89494-4-1yU8OlcZxj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89494-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89494
Piotr Kubaj <pkubaj at anongoth dot pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |WAITING
Resolution|FIXED |---
--- Comment #28 from Piotr Kubaj <pkubaj at anongoth dot pl> ---
I just tried on FreeBSD 12.2-RELEASE on powerpc64 with base gcc 4.2.1:
gmake[4]: Entering directory
'/wrkdirs/usr/ports/lang/gcc10-devel/work/.build/gcc'
c++ -std=gnu++98 -fno-PIE -c -DIN_GCC_FRONTEND -g -DIN_GCC
-fno-strict-aliasing -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W
-Wall -Wwrite-strings -Wcast-qual -Wno-format -Wmissing-format-attribute
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -I. -Icp
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/cp
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/../include
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/../libcpp/include
-I/usr/local/include
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/../libdecnumber
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/../libdecnumber/dpd
-I../libdecnumber
-I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/../libbacktrace
-DLIBICONV_PLUG -o cp/coroutines.o -MT cp/coroutines.o -MMD -MP -MF
cp/.deps/coroutines.TPo
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/cp/coroutines.cc
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/cp/coroutines.cc:2700:
error: invalid pure specifier (only `= 0' is allowed) before ';' token
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210313/gcc/cp/coroutines.cc:2700:
error: initializer specified for non-virtual method
'var_nest_node::var_nest_node()'
next prev parent reply other threads:[~2021-03-24 20:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-89494-4@http.gcc.gnu.org/bugzilla/>
2020-04-11 3:15 ` pkubaj at anongoth dot pl
2020-04-11 18:02 ` pkubaj at anongoth dot pl
2020-04-11 18:08 ` pkubaj at anongoth dot pl
2020-04-12 11:18 ` pkubaj at anongoth dot pl
2020-04-12 15:54 ` pkubaj at anongoth dot pl
2020-04-14 20:36 ` jakub at gcc dot gnu.org
2020-04-14 21:08 ` iains at gcc dot gnu.org
2020-04-14 21:13 ` jakub at gcc dot gnu.org
2020-04-15 12:20 ` jakub at gcc dot gnu.org
2020-04-15 13:17 ` cvs-commit at gcc dot gnu.org
2020-04-15 13:42 ` pkubaj at anongoth dot pl
2020-04-15 14:46 ` jakub at gcc dot gnu.org
2020-04-16 8:16 ` cvs-commit at gcc dot gnu.org
2020-05-01 1:36 ` pkubaj at anongoth dot pl
2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org
2021-03-24 20:03 ` iains at gcc dot gnu.org
2021-03-24 20:55 ` pkubaj at anongoth dot pl [this message]
2021-03-24 21:12 ` iains at gcc dot gnu.org
2021-04-10 17:03 ` pkubaj at anongoth dot pl
2024-03-17 4:18 ` iains at gcc dot gnu.org
2024-03-17 10:45 ` pkubaj at anongoth dot pl
2024-03-17 19:00 ` pinskia 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-89494-4-1yU8OlcZxj@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).