From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: George Barrett <bob@bob131.so>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/3] guile: fix make-value with pointer type
Date: Thu, 29 Jul 2021 12:55:57 -0400 [thread overview]
Message-ID: <1642874a-883c-5e8a-3a42-ed7ea95ccf71@polymtl.ca> (raw)
In-Reply-To: <wh-mj0-hb71xol&-i.3_czrd8a8m0ysong9_o/8cbk5&3f7denaq@mail.bob131.so>
I'll push it with this fixed:
> +/* Store in *MAX the largest value representable by pointer type
> + TYPE. */
I'll update this comment to reflect that the function now returns the
value.
Simon
next prev parent reply other threads:[~2021-07-29 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 15:12 [PATCH v3 1/3] gdbtypes: return value from get_unsigned_type_max George Barrett via Gdb-patches
2021-07-29 15:12 ` [PATCH v3 2/3] guile: fix make-value with pointer type George Barrett via Gdb-patches
2021-07-29 16:55 ` Simon Marchi via Gdb-patches [this message]
2021-07-29 15:12 ` [PATCH v3 3/3] guile/scm-math: indentation fixes George Barrett via Gdb-patches
2021-07-29 16:53 ` [PATCH v3 1/3] gdbtypes: return value from get_unsigned_type_max Simon Marchi via Gdb-patches
2021-07-29 17:01 ` George Barrett via Gdb-patches
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=1642874a-883c-5e8a-3a42-ed7ea95ccf71@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=bob@bob131.so \
--cc=simon.marchi@polymtl.ca \
/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