From: Hannes Domani <ssbssa@yahoo.de>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix heap-use-after-free in index-cached with --disable-threading
Date: Sat, 4 May 2024 16:28:45 +0000 (UTC) [thread overview]
Message-ID: <1542693138.10823446.1714840125123@mail.yahoo.com> (raw)
In-Reply-To: <878r0p1szk.fsf@tromey.com>
Am Samstag, 4. Mai 2024 um 17:45:06 MESZ hat Tom Tromey <tom@tromey.com> Folgendes geschrieben:
> >>>>> "Hannes" == Hannes Domani <ssbssa@yahoo.de> writes:
>
> Hannes> #else
> Hannes> /* Without threads, all the work is done immediately on the main
> Hannes> thread, and there is never anything to wait for. */
> Hannes> - done = true;
> Hannes> + done = desired_state == cooked_state::CACHE_DONE;
> Hannes> #endif /* CXX_STD_THREAD */
>
> I wouldn't mind if this code were lowered out of the #if, like:
>
>
> #endif /* CXX_STD_THREAD */
>
> bool done = ...
>
> However I think it's also fine as-is and can be tidied up later if
> anyone cares to.
Note that there is a small difference between them:
#if CXX_STD_THREAD
done = m_state == cooked_state::CACHE_DONE;
#else
done = desired_state == cooked_state::CACHE_DONE;
#endif
Though I wonder if not both could check for desired_state.
Hannes
next prev parent reply other threads:[~2024-05-04 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240504110942.922-1-ssbssa.ref@yahoo.de>
2024-05-04 11:09 ` Hannes Domani
2024-05-04 15:45 ` Tom Tromey
2024-05-04 16:28 ` Hannes Domani [this message]
2024-05-04 16:56 ` Hannes Domani
2024-05-10 5:59 ` Bernd Edlinger
2024-05-10 13:50 ` Hannes Domani
2024-05-10 18:03 ` Tom Tromey
2024-05-11 6:44 ` Bernd Edlinger
2024-05-10 19:16 ` Pedro Alves
2024-05-11 10:47 ` Hannes Domani
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=1542693138.10823446.1714840125123@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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