From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/build] Workaround gcc PR113599
Date: Thu, 25 Jan 2024 07:51:10 -0700 [thread overview]
Message-ID: <87bk99ii01.fsf@tromey.com> (raw)
In-Reply-To: <20240125142107.8643-1-tdevries@suse.de> (Tom de Vries's message of "Thu, 25 Jan 2024 15:21:07 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> However, I think it could be useful when bisecting gcc for other problems in
Tom> building gdb. Having this workaround means the bisect won't reintroduce the
Tom> problem. Furthermore, the workaround is harmless.
I think the change is harmless and well-documented, so I think it is ok.
Approved-By: Tom Tromey <tom@tromey.com>
thanks,
Tom
next prev parent reply other threads:[~2024-01-25 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 14:21 Tom de Vries
2024-01-25 14:51 ` Tom Tromey [this message]
2024-01-25 15:27 ` Sam James
2024-01-25 15:30 ` Tom de Vries
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=87bk99ii01.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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