From: Carl Love <cel@us.ibm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: Rogerio Alves <rogealve@br.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: RE: [PATCH ver3] gdb: Add PowerPC support to gdb.dwarf2/frame-inlined-in-outer-frame.exp
Date: Mon, 06 Dec 2021 10:06:02 -0800 [thread overview]
Message-ID: <a7899ad04de19db74577e65e61be7febb7cf14bb.camel@us.ibm.com> (raw)
In-Reply-To: <b489b388-8f45-29f3-0999-b616ba3f04bf@polymtl.ca>
Simon:
On Mon, 2021-12-06 at 11:43 -0500, Simon Marchi wrote:
> > +#if defined __powerpc64__
> > +# if _CALL_ELF == 2
> > +.abiversion 2 /* Tell gdb what ELF version to use. */
> > +.global _start
> > +_start:
> > +# else
> > +.abiversion 1 /* Tell gdb what ELF version to use. */
> > +.align 2
> > +.global _start
> > +.section ".opd", "aw"
> > +.align 3
> > +_start:
> > +.quad ._start,.TOC.@tocbase,0
> > +.previous
> > +.type ._start,@function
> > +._start:
> > +# endif
> > +#else
> > .global _start
> > _start:
> > +#endif
>
> My only question is whether these two lines:
>
> .global _start
> _start:
>
> could be kept unconditional, and just not put in the powerpc-specific
> sections of the code at all.
I chose to have them in the Power #if case with the .abiversion 2
statement and in the #else for all other architectures. On Power, we
must include .abiversion 2. I just don't know if on other platforms
.abiversion 2 is a valid statement or not? So, I chose not to include
it, i.e. don't change anything for other architectures to be sure I
don't break them. Basically, I took the most conservative approach as
I can't test all the other architectures.
Carl
next prev parent reply other threads:[~2021-12-06 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 21:43 [PATCH] " Carl Love
2021-11-29 23:22 ` will schmidt
2021-12-04 0:38 ` [PATCH ver2] " Carl Love
2021-12-04 2:13 ` Simon Marchi
2021-12-06 5:56 ` will schmidt
2021-12-06 16:37 ` [PATCH ver3] " Carl Love
2021-12-06 16:43 ` Simon Marchi
2021-12-06 18:06 ` Carl Love [this message]
2021-12-06 18:50 ` Simon Marchi
2021-12-06 19:35 ` Carl Love
2021-12-06 19:38 ` Simon Marchi
2021-12-07 8:37 ` Ulrich Weigand
[not found] ` <OF8B2BBF19.16E7F948-ONC12587A4.002F3132-C12587A4.002F617F@us.ibm.com>
2021-12-08 20:49 ` Carl Love
2021-12-09 17:30 ` Ulrich Weigand
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=a7899ad04de19db74577e65e61be7febb7cf14bb.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=rogealve@br.ibm.com \
--cc=simon.marchi@polymtl.ca \
--cc=will_schmidt@vnet.ibm.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).