Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: arnez@linux.vnet.ibm.com (Andreas Arnez)
Cc: gdb-patches@sourceware.org, sergiodj@redhat.com (Sergio Durigan Junior)
Subject: Re: [PATCH 4/4] S390: Vector ABI support
Date: Thu, 23 Apr 2015 16:07:00 -0000	[thread overview]
Message-ID: <20150423160739.19A56B8EB@oc7340732750.ibm.com> (raw)
In-Reply-To: <874mo882zc.fsf@br87z6lw.de.ibm.com> from "Andreas Arnez" at Apr 22, 2015 07:52:39 PM

Andreas Arnez wrote:

> 	* s390-linux-tdep.c: Include "elf/s390.h" and "elf-bfd.h".
> 	(enum s390_vector_abi_kind): New enum.
> 	(struct gdbarch_tdep)<vector_abi>: New field.
> 	(s390_effective_inner_type): Add parameter min_size.  Stop
> 	unwrapping if the inner type is smaller than min_size.
> 	(s390_function_arg_float): Adjust call to
> 	s390_effective_inner_type.
> 	(s390_function_arg_vector): New function.
> 	(s390_function_arg_integer): Adjust comment.
> 	(struct s390_arg_state)<vr>: New field.
> 	(s390_handle_arg): Add parameter 'is_vararg'.  Pass vector
> 	arguments according to vector ABI when appropriate.
> 	(s390_push_dummy_call): Initialize the argument state's field
> 	'vr'.  Adjust calls to s390_handle_arg.
> 	(s390_register_return_value): Handle vector return values.
> 	(s390_return_value): Apply the "register" return value convention
> 	to a vector when appropriate.
> 	(s390_gdbarch_init): Initialize tdep->vector_abi.

> 	* NEWS: Announce S390 vector ABI support.

The NEWS change needs to be approved by Eli.


>  static void
>  s390_handle_arg (struct s390_arg_state *as, struct value *arg,
>  		 struct gdbarch_tdep *tdep, int word_size,
> -		 enum bfd_endian byte_order)
> +		 enum bfd_endian byte_order, int is_vararg)

Maybe "is_unnamed" would be better than "is_vararg".

> +  /* Determine vector ABI.  */
> +  if (have_vx
> +      && info.abfd != NULL
> +      && info.abfd->format == bfd_object
> +      && bfd_get_flavour (info.abfd) == bfd_target_elf_flavour
> +      && bfd_elf_get_obj_attr_int (info.abfd, OBJ_ATTR_GNU,
> +				   Tag_GNU_S390_ABI_Vector) == 2)

I think this needs to be under an #ifdef HAVE_ELF, otherwise we'd
get compile errors when building GDB on a non-ELF host system.


Otherwise, this is OK once the binutils patch is committed.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2015-04-23 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 17:45 [PATCH 0/4] " Andreas Arnez
2015-04-22 17:49 ` [PATCH 1/4] S390: For zero, let is_power_of_two() return false Andreas Arnez
2015-04-23 16:02   ` Ulrich Weigand
2015-04-22 17:51 ` [PATCH 3/4] S390: Re-arrange implementation of s390_return_value Andreas Arnez
2015-04-23 16:03   ` Ulrich Weigand
2015-04-22 17:51 ` [PATCH 2/4] S390: Restructure s390_push_dummy_call Andreas Arnez
2015-04-23 16:03   ` Ulrich Weigand
2015-04-22 17:52 ` [PATCH 4/4] S390: Vector ABI support Andreas Arnez
2015-04-22 17:58   ` Andreas Arnez
2015-04-23 16:07   ` Ulrich Weigand [this message]
2015-04-24 14:46     ` Andreas Arnez
2015-04-23 16:47   ` Eli Zaretskii
2015-04-27  9:41 ` [PATCH 0/4] " Andreas Krebbel

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=20150423160739.19A56B8EB@oc7340732750.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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