public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/111021] [14 Regression] Serial build broken for CRIS, ARM, and others
Date: Tue, 15 Aug 2023 05:04:48 +0000 [thread overview]
Message-ID: <bug-111021-4-dn218plCw8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111021-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111021
--- Comment #8 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #6)
>
> btw, thanks for the suggestion on "defaulting to NULL or something" in ML,
> but I guess a default value like zero rather than ERROR_MARK has to base on
> the assertion that the default value is equal to ERROR_MARK, IMHO it isn't
> quite maintainable.
I believe you could add a code_helper constructor for another type, maybe even
"int"? Then the "default" value for the code_helper argument for the
legitimate address hook function would just look like "code_helper = 0".
Maybe that's too error-prone and a pointer-type or some entirely different type
would be better. I might have misunderstood things of course, but that's what I
mean by "or something".
next prev parent reply other threads:[~2023-08-15 5:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 3:04 [Bug bootstrap/111021] New: " hp at gcc dot gnu.org
2023-08-15 3:17 ` [Bug bootstrap/111021] " pinskia at gcc dot gnu.org
2023-08-15 3:27 ` linkw at gcc dot gnu.org
2023-08-15 3:29 ` hp at gcc dot gnu.org
2023-08-15 3:32 ` hp at gcc dot gnu.org
2023-08-15 4:07 ` hp at gcc dot gnu.org
2023-08-15 4:39 ` linkw at gcc dot gnu.org
2023-08-15 4:44 ` hp at gcc dot gnu.org
2023-08-15 5:04 ` hp at gcc dot gnu.org [this message]
2023-08-15 5:22 ` hp at gcc dot gnu.org
2023-08-15 5:31 ` linkw at gcc dot gnu.org
2023-08-15 5:33 ` hp at gcc dot gnu.org
2023-08-15 7:05 ` rguenth at gcc dot gnu.org
2023-08-15 7:23 ` linkw at gcc dot gnu.org
2023-08-15 7:33 ` linkw at gcc dot gnu.org
2023-08-15 8:06 ` cvs-commit at gcc dot gnu.org
2023-08-15 9:03 ` rguenth at gcc dot gnu.org
2023-08-15 10:54 ` cvs-commit at gcc dot gnu.org
2023-08-15 11:04 ` hp at gcc dot gnu.org
2023-08-18 10:08 ` cvs-commit at gcc dot gnu.org
2023-08-18 10:13 ` [Bug bootstrap/111021] [14 Regression] Serial build broken for CRIS, ARM, and others since r14-3092 linkw 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-111021-4-dn218plCw8@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).