From: Andrew Burgess <aburgess@redhat.com>
To: "Kempke\, Nils-Christian" <nils-christian.kempke@intel.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/5] Solve caching problems with compiler_info
Date: Thu, 09 Jun 2022 14:42:48 +0100 [thread overview]
Message-ID: <87ilpaeyw7.fsf@redhat.com> (raw)
In-Reply-To: <CY4PR1101MB20714FB8B45638212F32A5CEB8A49@CY4PR1101MB2071.namprd11.prod.outlook.com>
"Kempke, Nils-Christian via Gdb-patches" <gdb-patches@sourceware.org>
writes:
>> -----Original Message-----
>> From: Gdb-patches <gdb-patches-bounces+nils-
>> christian.kempke=intel.com@sourceware.org> On Behalf Of Andrew
>> Burgess via Gdb-patches
>> Sent: Wednesday, June 8, 2022 4:22 PM
>> To: gdb-patches@sourceware.org
>> Cc: Andrew Burgess <aburgess@redhat.com>
>> Subject: [PATCH 0/5] Solve caching problems with compiler_info
>>
>> This series is an alternative proposal to solve the caching problems
>> with compiler_info.
>>
>> Patch #1 is taken unmodified from Nils' v2 series.
>>
>> Patches #2, #3, #4, and #5 are new work, though the final patch
>> addresses the same problem as the second patch in Nils' v2 series.
>>
>> Thanks,
>> Andrew
>
>
> Hi Andrew,
>
> Thanks for this - I only had two minor comments really. The rest of this
> series is nice. I do prefer it over my initially submitted patches. And thanks
> for showing how the associative array works !
Thanks for the feedback.
As this issue was causing significant test failures when not running
tests in parallel, I've gone ahead and pushed this (with the updated
patch #2).
I'm happy to address any feedback that comes up later.
Thanks,
Andrew
next prev parent reply other threads:[~2022-06-09 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 10:16 [PATCH v2 0/2] Fix regressions introduced by Fortran compiler identification series Nils-Christian Kempke
2022-06-07 10:16 ` [PATCH v2 1/2] gdb/testsuite: use test_compiler_info in gcc_major_version Nils-Christian Kempke
2022-06-08 9:50 ` Andrew Burgess
2022-06-07 10:16 ` [PATCH v2 2/2] gdb/testsuite: cache compiler_info on a per language basis Nils-Christian Kempke
2022-06-08 14:18 ` Andrew Burgess
2022-06-08 14:22 ` [PATCH 0/5] Solve caching problems with compiler_info Andrew Burgess
2022-06-08 14:22 ` [PATCH 1/5] gdb/testsuite: use test_compiler_info in gcc_major_version Andrew Burgess
2022-06-08 14:22 ` [PATCH 2/5] gdb/testsuite: remove unneeded get_compiler_info calls from gdb.exp Andrew Burgess
2022-06-09 13:39 ` Andrew Burgess
2022-06-08 14:22 ` [PATCH 3/5] gdb/testsuite: make 'c' default language for get/test compiler info Andrew Burgess
2022-06-08 16:06 ` Kempke, Nils-Christian
2022-06-09 13:40 ` Andrew Burgess
2022-06-08 14:22 ` [PATCH 4/5] gdb/testsuite: handle errors better in test_compiler_info Andrew Burgess
2022-06-08 14:22 ` [PATCH 5/5] gdb/testsuite: solve problems with compiler_info caching Andrew Burgess
2022-06-08 16:21 ` [PATCH 0/5] Solve caching problems with compiler_info Kempke, Nils-Christian
2022-06-09 13:42 ` Andrew Burgess [this message]
2022-06-09 16:25 ` Tom de Vries
2022-06-10 11:03 ` Andrew Burgess
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=87ilpaeyw7.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=nils-christian.kempke@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).