From: Simon Marchi <simark@simark.ca>
To: Carl Love <cel@us.ibm.com>, Bruno Larsen <blarsen@redhat.com>,
gdb-patches@sourceware.org,
UlrichWeigand <Ulrich.Weigand@de.ibm.com>,
pedro@palves.net
Cc: luis.machado@arm.com
Subject: Re: [PATCH 2/2 v5] Fix reverse stepping multiple contiguous PC ranges over the line table.
Date: Fri, 23 Jun 2023 13:49:22 -0400 [thread overview]
Message-ID: <4af9b32a-540c-43d8-69b7-f9f16aeb0811@simark.ca> (raw)
In-Reply-To: <93bd0e348673cf870b5fe20b5f3a2760fe5ef3a4.camel@us.ibm.com>
On 6/22/23 16:38, Carl Love wrote:
> Simon:
>
> On Mon, 2023-06-19 at 13:58 -0400, Simon Marchi wrote:
> <snip>
>
>>
> 100644
>>> --- a/gdb/infrun.c
>>> +++ b/gdb/infrun.c
>>> @@ -114,6 +114,9 @@ static struct async_event_handler
>>> *infrun_async_inferior_event_token;
>>> Starts off as -1, indicating "never enabled/disabled". */
>>> static int infrun_is_async = -1;
>>>
>>> +static CORE_ADDR update_line_range_start (CORE_ADDR pc,
>>> + struct
>>> execution_control_state *ecs);
>>> +
>>
>> This forward-declaration is not needed.
>
> I tried removing the forward-declaration and the compile fails with the
> message:
>
> ../../binutils-gdb-reverse-multiple-contiguous/gdb/infrun.c:6773:1:
> error: no previous declaration for ‘CORE_ADDR
> update_line_range_start(CORE_ADDR, execution_control_state*)’ [-
> Werror=missing-declarations]
> 6773 | update_line_range_start (CORE_ADDR pc, struct
> execution_control_state *ecs)
> | ^~~~~~~~~~~~~~~~~~~~~~~
> cc1plus: all warnings being treated as errors
> make[2]: *** [Makefile:1922: infrun.o] Error 1
> make[2]: Leaving directory '/home/carll/GDB/build-reverse-multiple-
> contiguous/gdb'
> make[1]: *** [Makefile:13569: all-gdb] Error 2
> make[1]: Leaving directory '/home/carll/GDB/build-reverse-multiple-
> contiguous'
> make: *** [Makefile:1005: all] Error 2
>
> Leaving the forward declaration in the code.
Because you need to put "static" at the other place (line 6813).
Simon
next prev parent reply other threads:[~2023-06-23 17:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 20:59 [PATCH] " Carl Love
2023-05-02 14:15 ` Bruno Larsen
2023-05-02 15:40 ` Carl Love
2023-05-02 15:42 ` Bruno Larsen
2023-05-11 15:11 ` Simon Marchi
2023-05-03 9:53 ` Bruno Larsen
2023-05-04 2:55 ` Carl Love
2023-05-04 9:24 ` Bruno Larsen
2023-05-04 14:52 ` Carl Love
2023-05-04 2:55 ` [PATCH v2] " Carl Love
2023-05-04 15:59 ` [PATCH v3] " Carl Love
2023-05-05 14:59 ` Luis Machado
2023-05-05 16:10 ` Carl Love
2023-05-10 13:47 ` Bruno Larsen
2023-05-10 17:16 ` Carl Love
2023-05-10 17:32 ` [PATCH v4] " Carl Love
2023-05-11 16:01 ` Simon Marchi
2023-05-11 16:23 ` Bruno Larsen
2023-05-11 17:28 ` Simon Marchi
2023-05-16 22:54 ` [PATCH 1/2] " Carl Love
2023-06-19 17:11 ` Simon Marchi
2023-06-22 16:52 ` Carl Love
2023-06-23 17:44 ` Simon Marchi
2023-06-23 19:41 ` Carl Love
2023-06-23 20:04 ` [PATCH 1/2 ver 2] " Carl Love
2023-07-06 15:07 ` Carl Love
2023-05-16 22:54 ` [PATCH 2/2 v5] " Carl Love
2023-05-25 15:08 ` Carl Love
2023-06-08 16:36 ` Carl Love
2023-06-19 17:58 ` Simon Marchi
2023-06-22 20:38 ` Carl Love
2023-06-22 20:39 ` Carl Love
2023-06-23 17:49 ` Simon Marchi [this message]
2023-06-23 20:04 ` Carl Love
2023-06-23 20:04 ` [PATCH 2/2 v6] " Carl Love
2023-05-16 22:54 ` [PATCH v4] " Carl Love
2023-05-11 7:52 ` [PATCH v3] " Bruno 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=4af9b32a-540c-43d8-69b7-f9f16aeb0811@simark.ca \
--to=simark@simark.ca \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=blarsen@redhat.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=pedro@palves.net \
/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).