From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/gdbserver] x86 LynxOS-178: Adjust floating-point context structure
Date: Thu, 10 May 2018 16:47:00 -0000 [thread overview]
Message-ID: <a8a05a11fba0a13b706672d447621d7e@polymtl.ca> (raw)
In-Reply-To: <1525964730-8822-2-git-send-email-brobecker@adacore.com>
On 2018-05-10 11:05, Joel Brobecker wrote:
> The floating point context structure on x86 LynxOS-178 is not
> the same as on LynxOS 5.x. As a consequence, trying to print
> the return value of a function returning a float, for instance,
> yields incorrect results.
>
> This patch fixes the issue by providing an updated definition
> for LynxOS-178 (the reason why we cannot access the actual definition
> provided by the system still remains true).
>
> gdb/gdbserver/ChangeLog:
>
> * lynx-i386-low.c (LYNXOS_178): New macro.
> (usr_fcontext_t) <LYNXOS_178>: Provide a definition that
> matches
> the layout on LynxOS-178.
This syntax (with < >) is usually meant to denote fields (as if you were
referring to field LYNXOS_178 in structure usr_fcontext_t). To denote
an #ifdef context (which is what I understand you want to do), I usually
see this syntax:
[LYNXOS_178] (usr_fcontext_t): ...
For example:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/ChangeLog-2017;h=aaadf142a4641ecd3feb26bc1dfa83dcc19e713c;hb=HEAD#l13806
> (lynx_i386_fill_fpregset, lynx_i386_store_fpregset): Do not
> handle floating point registers that are not supported by
> LynxOS-178.
>
> OK to push to master?
Otherwise, it looks good to me.
Simon
next prev parent reply other threads:[~2018-05-10 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:16 GDBserver patch for x86 LynxOS-178 Joel Brobecker
2018-05-10 15:38 ` [RFA/gdbserver] x86 LynxOS-178: Adjust floating-point context structure Joel Brobecker
2018-05-10 16:47 ` Simon Marchi [this message]
2018-05-10 18:34 ` Joel Brobecker
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=a8a05a11fba0a13b706672d447621d7e@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.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