From: Luis Machado <luis.machado@linaro.org>
To: Tom Tromey <tom@tromey.com>
Cc: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/6] Use a std::vector in target_section_table
Date: Wed, 14 Oct 2020 10:01:44 -0300 [thread overview]
Message-ID: <dd549396-6929-5bab-d220-7d91b14da3cc@linaro.org> (raw)
In-Reply-To: <875z7dq80k.fsf@tromey.com>
On 10/14/20 9:58 AM, Tom Tromey wrote:
> Luis> From seeing the before/after log files, I only noticed differences in
> Luis> the values printed. Maybe something is not getting relocated/reloaded
> Luis> properly?
>
> I tried on gcc113 today and couldn't reproduce the bug.
I have a Ubuntu 18.04 system with the standard GCC 7.5.0. What OS is
gcc113 running?
next prev parent reply other threads:[~2020-10-14 13:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 19:37 [PATCH 0/6] Change target section table management Tom Tromey
2020-10-03 19:37 ` [PATCH 1/6] Introduce target-section.h Tom Tromey
2020-10-04 8:29 ` Andrew Burgess
2020-10-09 1:17 ` Tom Tromey
2020-10-03 19:37 ` [PATCH 2/6] Use a std::vector in target_section_table Tom Tromey
2020-10-13 16:41 ` Luis Machado
2020-10-13 20:35 ` Tom Tromey
2020-10-13 22:48 ` Luis Machado
2020-10-14 12:58 ` Tom Tromey
2020-10-14 13:01 ` Luis Machado [this message]
2020-10-14 13:18 ` Tom Tromey
2020-10-14 13:23 ` Luis Machado
2020-10-14 14:06 ` Simon Marchi
2020-10-14 9:09 ` Tom de Vries
2020-11-10 17:38 ` Simon Marchi
2020-10-03 19:37 ` [PATCH 3/6] build_section_table cannot fail Tom Tromey
2020-10-04 8:38 ` Andrew Burgess
2020-10-03 19:37 ` [PATCH 4/6] Simplify add_target_sections_of_objfile Tom Tromey
2020-10-04 8:40 ` Andrew Burgess
2020-10-03 19:37 ` [PATCH 5/6] Remove clear_section_table Tom Tromey
2020-10-04 8:44 ` Andrew Burgess
2020-10-03 19:37 ` [PATCH 6/6] Change target_section_table to std::vector alias Tom Tromey
2020-10-04 8:46 ` Andrew Burgess
2020-10-13 2:19 ` [PATCH 0/6] Change target section table management 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=dd549396-6929-5bab-d220-7d91b14da3cc@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).