public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug guile/30767] [gdb/guile, build, c++20] Werror=volatile in SCM_UNPACK
Date: Wed, 16 Aug 2023 06:51:13 +0000 [thread overview]
Message-ID: <bug-30767-4717-yFYCNg2Rtq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30767-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30767
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #1)
> The code can't be run so it is probably just some syntactic check.
It is, this is with the default SCM_DEBUG_TYPING_STRICTNESS == 1, I suppose if
needed we could work around this by defining to 2 or 0.
See https://fossies.org/linux/guile/libguile/scm.h
> Anyway it should be reported to Guile.
Done.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65333
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-08-16 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 18:25 [Bug guile/30767] New: " vries at gcc dot gnu.org
2023-08-15 21:36 ` [Bug guile/30767] " tromey at sourceware dot org
2023-08-16 6:51 ` vries at gcc dot gnu.org [this message]
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-30767-4717-yFYCNg2Rtq@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).