From: Tom Tromey <tom@tromey.com>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] gdb: Start supporting AVX instruction
Date: Thu, 06 Jun 2024 11:01:17 -0600 [thread overview]
Message-ID: <87bk4em2ea.fsf@tromey.com> (raw)
In-Reply-To: <4e69730a-faba-4c05-b68d-264942d7d1e8@redhat.com> (Guinevere Larsen's message of "Wed, 5 Jun 2024 14:33:51 -0300")
>>>>> "Guinevere" == Guinevere Larsen <blarsen@redhat.com> writes:
>> I wouldn't be surprised to get some kind of dead code warning here,
>> since the switch only has a single branch.
Guinevere> no warnings in my system... but that is possible, I guess. Do you
Guinevere> think it would be better to merge this commit with the following one?
I wouldn't worry about it.
Tom
next prev parent reply other threads:[~2024-06-06 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 20:27 [PATCH 0/3] Small step in supporting AVX instructions Guinevere Larsen
2024-05-21 20:27 ` [PATCH 1/3] gdb: Start supporting AVX instruction Guinevere Larsen
2024-06-05 16:11 ` Tom Tromey
2024-06-05 17:33 ` Guinevere Larsen
2024-06-06 17:01 ` Tom Tromey [this message]
2024-05-21 20:27 ` [PATCH 2/3] gdb/record: add support to vmovd and vmovq instructions Guinevere Larsen
2024-06-05 16:13 ` Tom Tromey
2024-06-05 18:24 ` Guinevere Larsen
2024-06-05 19:53 ` Guinevere Larsen
2024-05-21 20:28 ` [PATCH 3/3] gdb/record: add support to AVX unpack instructions Guinevere Larsen
2024-06-04 19:10 ` [PING][PATCH 0/3] Small step in supporting AVX instructions Guinevere Larsen
2024-06-05 16:13 ` Tom Tromey
2024-06-06 8:16 ` Willgerodt, Felix
2024-06-06 12:50 ` Guinevere Larsen
2024-06-06 13:36 ` Willgerodt, Felix
2024-06-06 13:45 ` Guinevere Larsen
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=87bk4em2ea.fsf@tromey.com \
--to=tom@tromey.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@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