public inbox for gdb-patches@sourceware.org
 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] Add vector ABI tests to gnu_vector.exp
Date: Fri, 12 Jun 2015 15:48:00 -0000	[thread overview]
Message-ID: <20150612154853.53B9C12CF@oc7340732750.ibm.com> (raw)
In-Reply-To: <87617wa3wi.fsf@br87z6lw.de.ibm.com> from "Andreas Arnez" at May 13, 2015 05:33:17 PM

Andreas Arnez wrote:

> So far the gnu_vector test was limited to "static" aspects of GDB's
> vector support, like evaluating vector-valued expressions.  This patch
> enriches the test and adds checks for GDB's vector ABI support as well.
> The new checks particularly verify inferior function calls with vector
> arguments and GDB's handling of vector return values.
> 
> The test now attempts to compile for the target's "native" architecture,
> such that a hardware vector ABI is used if available.

This is certainly a good idea.  (In fact, the tests uncovered a bug in
the ABI implementation on PowerPC.  I've just committed a fix for that.)

> Since GDB has no vector ABI support for x86 and x86_64 targets, most of
> the new checks are XFAILed there.

As this due to a known GDB problem and not something in the environment,
that should be a KFAIL, not an XFAIL.

> gdb/testsuite/ChangeLog:
> 
> 	* gdb.base/gnu_vector.c: Include stdarg.h and stdio.h.
> 	(VECTOR): New macro.  Use it...
> 	(int4, uint4, char4, float4, int2, longlong2, float2, double2):
> 	...for these typedefs.
> 	(int8, char1, int1, double1): New typedefs.
> 	(struct just_int2, struct two_int2): New structures.
> 	(add_some_intvecs, add_many_charvecs, add_various_floatvecs,
> 	(add_structvecs, add_singlevecs): New functions.
> 	(main): Call add_some_intvecs twice.
> 	* gdb.base/gnu_vector.exp: Drop GCC version check; just attempt
> 	the compile and exit upon failure.  Try compiling for the "native"
> 	architecture.  Test inferior function calls with vector arguments
> 	and vector return value handling with "finish" and "return".

Otherwise, this looks good.

Bye,
Ulrich

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

  reply	other threads:[~2015-06-12 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 15:33 Andreas Arnez
2015-06-12 15:48 ` Ulrich Weigand [this message]
2015-06-15 16:05   ` Andreas Arnez
2015-06-16 11:41     ` 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=20150612154853.53B9C12CF@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).