From: Simon Marchi <simark@simark.ca>
To: "Balasubrmanian, Vignesh" <Vignesh.Balasubrmanian@amd.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
"Kumar N, Bhuvanendra" <Bhuvanendra.KumarN@amd.com>
Subject: Re: [PATCH 1/2] Add lld(linker) specific option.
Date: Mon, 21 Mar 2022 09:44:57 -0400 [thread overview]
Message-ID: <f062622d-27c7-07ef-2daf-9d11dfdbae28@simark.ca> (raw)
In-Reply-To: <CY4PR12MB1814481686B68A7D12FD0F7087169@CY4PR12MB1814.namprd12.prod.outlook.com>
On 2022-03-21 08:15, Balasubrmanian, Vignesh via Gdb-patches wrote:
>
> Please review the attached patch.
>
> LLD doesn't have the option "-Ttext-segment" but "--image-base".
> So first try using "-Ttext-segment". If it fails, try the lld option "--image-base" before failing.
>
> Thanks,
> vigneshbalu
>
>
Hi,
The approach looks ok to me.
Grepping for "text-segment", I see three other tests using
-Ttext-segment, are we going to need to fix those up too?
- gdb.base/execl-update-breakpoints.exp
- gdb.arch/arm-bl-branch-dest.exp
- gdb.threads/step-over-exec.exp
If so, it would be interesting to make this an option to gdb_compile,
instead of specifying a linker-specific flag. For example, you'd use:
set options [list \
additional_flags=-DFUNCTION_NAME=[format "jit_function_%04d" $i] \
text_segment=$addr]
and text_segment would be recognized by gdb_compile and the complexity
would be hidden there.
Can you mention (here and in the commit message) the full "make check"
line you use to test this?
Simon
next prev parent reply other threads:[~2022-03-21 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 12:15 Balasubrmanian, Vignesh
2022-03-21 13:44 ` Simon Marchi [this message]
2022-03-22 16:21 ` Balasubrmanian, Vignesh
2022-03-29 8:35 ` Luis Machado
2022-03-29 12:21 ` Simon Marchi
2022-03-29 12:23 ` Simon Marchi
2022-03-30 11:21 ` Balasubrmanian, Vignesh
2022-04-18 14:27 ` Simon Marchi
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=f062622d-27c7-07ef-2daf-9d11dfdbae28@simark.ca \
--to=simark@simark.ca \
--cc=Bhuvanendra.KumarN@amd.com \
--cc=JiniSusan.George@amd.com \
--cc=Vignesh.Balasubrmanian@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).