This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix complex argument handling in ppc64 dummy function call
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Tiago StÃrmer Daitx <tdaitx at linux dot vnet dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 01 Mar 2013 15:57:02 -0300
- Subject: Re: [PATCH] Fix complex argument handling in ppc64 dummy function call
- References: <20130301170811.EFEA2300943@igoo.rch.stglabs.ibm.com>
On Friday, March 01 2013, Tiago StÃrmer Daitx wrote:
> Sergio, many thanks for the thorough review and the tips. There's no better
> way to get these rules to stick in my head. ^_^
Thanks a lot!
> Let me know if there is still something amiss.
Just one little thing :-).
> + else if (TYPE_CODE (type) == TYPE_CODE_COMPLEX
> + && (TYPE_LENGTH (type) == 8 || TYPE_LENGTH (type) == 16))
> + {
> + int i;
> +
> + for (i = 0; i < 2; i++)
> + {
> + if (write_pass)
> + {
> + struct type *target_type;
> +
> + target_type = check_typedef (TYPE_TARGET_TYPE (type));
> + ppc64_sysv_abi_push_float (gdbarch, regcache, tdep,
> + target_type, val + i *
> + TYPE_LENGTH (target_type),
> + freg, greg, gparam);
> + }
> + freg++;
> + greg++;
> + /* Always consume parameter stack space. */
> + gparam = align_up(gparam + 8, tdep->wordsize);
Space between the function name and its arguments. It should read:
align_up (gparam....);
But don't bother sending the patch again just for that little nit. When
the patch gets reviewed/accepted, just commit it with the proper fix
:-).
Thanks again,
--
Sergio