public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/110284] [14 Regression] Bootstrap failures with m2
Date: Tue, 20 Jun 2023 22:00:46 +0000 [thread overview]
Message-ID: <bug-110284-4-sZLSXY8E6w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110284-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110284
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
I have seen (but this is random, I guess depending on the order in which builds
occur):
In file included from /src-local/arsen/gcc/m2/gm2-gcc/gcc-consolidation.h:71,
from /src-local/arsen/gcc/m2/m2.flex:23:
24 | #include "insn-opinit.h"
If I can repeat will add more here.
next prev parent reply other threads:[~2023-06-20 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 12:40 [Bug modula2/110284] New: " jakub at gcc dot gnu.org
2023-06-16 12:40 ` [Bug modula2/110284] " jakub at gcc dot gnu.org
2023-06-17 21:07 ` gaius at gcc dot gnu.org
2023-06-18 14:58 ` gaius at gcc dot gnu.org
2023-06-18 15:01 ` jakub at gcc dot gnu.org
2023-06-18 19:23 ` gaius at gcc dot gnu.org
2023-06-18 20:08 ` cvs-commit at gcc dot gnu.org
2023-06-18 20:14 ` gaius at gcc dot gnu.org
2023-06-18 20:52 ` jakub at gcc dot gnu.org
2023-06-18 21:24 ` gaius at gcc dot gnu.org
2023-06-20 17:04 ` jakub at gcc dot gnu.org
2023-06-20 17:23 ` jakub at gcc dot gnu.org
2023-06-20 22:00 ` iains at gcc dot gnu.org [this message]
2023-06-23 15:08 ` gaius at gcc dot gnu.org
2023-07-19 8:49 ` jakub at gcc dot gnu.org
2023-07-19 16:07 ` gaius at gcc dot gnu.org
2023-07-19 20:02 ` cvs-commit at gcc dot gnu.org
2023-07-19 20:08 ` gaius at gcc dot gnu.org
2023-07-31 18:44 ` cvs-commit 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-110284-4-sZLSXY8E6w@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).