From: Alan Hayward <Alan.Hayward@arm.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH v3 3/3] Aarch64: Fix segfault when casting dummy calls
Date: Tue, 23 Oct 2018 16:08:00 -0000 [thread overview]
Message-ID: <9290BC71-862C-48B1-97FD-A46C5D15A65C@arm.com> (raw)
In-Reply-To: <95a5dd34-6815-f3f5-107c-13f4956b741e@redhat.com>
> On 19 Oct 2018, at 12:35, Pedro Alves <palves@redhat.com> wrote:
>
<snip>
>> to calculate lang_struct_return. This information is available in the
>> return_method enum. The fix is to simply use this instead.
>>
>> Add common test case using a shared library to ensure FUNC resolving.
>
> What does "common" mean here?
By common I just meant not-aarch64-specific. I guess what I really meant
was any target that supported shared libraries.
>
> And what does "to ensure FUNC resolving" mean too, btw?
> AFAICT, the only reason to use a shared library is to
> compile it with or without debug information, right?
> Come to think of it, you could instead eliminate the
> shared library and compile a separate .o file instead, right?
> That would simplify the testcase a bit and expose it to more
> targets.
>
I could only get the bug to expose itself when using a .so
If I do the following using current HEAD then the bug is not present:
g++ -c condbreak-solib-main.cc -o condbreak-solib-main.o -fno-inline
g++ -c condbreak-solib-lib.cc -o condbreak-solib-lib.o -fno-inline
g++ condbreak-solib-main.o condbreak-solib-lib.o
It causes the type of the return value to be detected as
TYPE_CODE_PTR->TYPE_CODE_INT.
Or was there another method you were thinking?
"Ok" for all the other comments (including 1/3 and 2/3).
As a side note, many of the GNU style issues I kept hitting in the tests
are due to me relying too much on check_GNU_style.sh (from gcc) which
ignores any files in the testsuite directory. Tools are great, until
they aren’t :)
Alan.
next prev parent reply other threads:[~2018-10-23 16:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 14:49 [PATCH v3 0/3] " Alan Hayward
2018-10-11 14:49 ` [PATCH v3 3/3] " Alan Hayward
2018-10-19 11:36 ` Pedro Alves
2018-10-23 16:08 ` Alan Hayward [this message]
2018-10-24 15:15 ` Pedro Alves
2018-10-29 11:58 ` Alan Hayward
2018-10-29 12:38 ` Pedro Alves
2018-10-29 14:56 ` Alan Hayward
2018-10-29 18:13 ` Pedro Alves
2018-10-30 11:13 ` Alan Hayward
2018-10-30 16:31 ` Pedro Alves
2018-10-30 17:09 ` Alan Hayward
2018-10-30 17:40 ` Pedro Alves
2018-10-11 14:49 ` [PATCH v3 2/3] Pass return_method to _push_dummy_call Alan Hayward
2018-10-19 11:31 ` Pedro Alves
2018-10-11 14:49 ` [PATCH v3 1/3] Use enum for return method for dummy calls Alan Hayward
2018-10-19 11:28 ` Pedro Alves
2018-10-18 9:50 ` [PING][PATCH v3 0/3] Aarch64: Fix segfault when casting " Alan Hayward
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=9290BC71-862C-48B1-97FD-A46C5D15A65C@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=palves@redhat.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).