From: Andreas Schwab <schwab@linux-m68k.org>
To: Simon Marchi <simark@simark.ca>
Cc: Guinevere Larsen <guinevere@redhat.com>,
Andrew Oates <andrew@andrewoates.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix compile error due to [[noreturn]] with clang
Date: Tue, 22 Oct 2024 22:53:50 +0200 [thread overview]
Message-ID: <877c9z6eqp.fsf@igel.home> (raw)
In-Reply-To: <9f436087-d5c5-449a-b80c-da896989fc4e@simark.ca> (Simon Marchi's message of "Tue, 22 Oct 2024 16:37:07 -0400")
On Okt 22 2024, Simon Marchi wrote:
> On 2024-10-22 16:20, Andreas Schwab wrote:
>> On Okt 22 2024, Simon Marchi wrote:
>>
>>> So, I can't reproduce the build failure when configuring with
>>> `--enable-targets=all --enable-sim`. It looks like remote-sim.o doesn't
>>> get built, which is odd given that the simulator is enabled. Sounds
>>> like a bug?
>>
>> It's only enabled for the main gdb target.
>>
>
> But nowadays, --enable-targets=all builds the sim for all targets (that
> have a sim), not only the main target. Would it be possible to build
> remote-sim.o in that case, and use the simulator for any target, from a
> single --enable-targets=all gdb build?
There can only be one simulator linked into gdb.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2024-10-22 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 18:00 andrew
2024-10-22 18:28 ` Guinevere Larsen
2024-10-22 18:50 ` Andrew Oates
2024-10-22 19:10 ` Guinevere Larsen
2024-10-22 19:25 ` Andrew Oates
2024-10-22 19:37 ` Simon Marchi
2024-10-22 20:20 ` Andreas Schwab
2024-10-22 20:37 ` Simon Marchi
2024-10-22 20:53 ` Andreas Schwab [this message]
2024-10-24 0:40 ` Andrew Oates
2024-10-25 15:36 ` Tom Tromey
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=877c9z6eqp.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=andrew@andrewoates.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=simark@simark.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