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: qiyaoltc@gmail.com (Yao Qi), dje@google.com (Doug Evans),
	       brobecker@adacore.com (Joel Brobecker),
	       gdb-patches@sourceware.org (gdb-patches)
Subject: Re: Several regressions and we branch soon.
Date: Fri, 10 Jul 2015 16:23:00 -0000	[thread overview]
Message-ID: <20150710162332.182E6B042@oc7340732750.ibm.com> (raw)
In-Reply-To: <87zj34j8kl.fsf@br87z6lw.de.ibm.com> from "Andreas Arnez" at Jul 10, 2015 06:12:10 PM

Andreas Arnez wrote:
> On Fri, Jul 10 2015, Yao Qi wrote:

> GCC5 on ppc64le emits the ABI warning even in absence of "-mcpu=".
> Again it should help to add "-Wno-psabi".

Yes, for ppc64 we definitely should add -Wno-psabi.

> Yes.  But in this case no vector ABI is used, because that test machine
> does not have a vector facility and because -march=native is not
> supported by GCC (yet).  Thus vector return values are not passed in
> vector registers, but according to RETURN_VALUE_STRUCT_CONVENTION.  And
> then we hit the problem that displaying such return values is not
> supported by GDB: https://sourceware.org/bugzilla/show_bug.cgi?id=8549

Hmm.  Since this is a separate problem independent of vector support,
maybe this test case should accept the failure to display struct return
values, and pass the test (or maybe KFAIL?).

Bye,
Ulrich

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


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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 18:31 Doug Evans
2015-06-23 18:55 ` Patrick Palka
2015-06-23 19:03   ` Doug Evans
2015-06-23 20:17     ` Keith Seitz
2015-06-23 20:53       ` Doug Evans
2015-06-23 21:45         ` Patrick Palka
2015-06-24 11:55           ` Yao Qi
2015-06-25 16:35             ` Tedeschi, Walfred
2015-07-01  8:49               ` Yao Qi
     [not found]                 ` <AC542571535E904D8E8ADAE745D60B1944445D44@IRSMSX104.ger.corp.intel.com>
2015-07-01  9:30                   ` Walfred Tedeschi
2015-07-02 10:09                     ` Yao Qi
2015-07-02 15:34           ` Yao Qi
2015-07-02 16:19             ` [PATCH] Don't throw an error in "show mpx bound" implementation Patrick Palka
2015-07-06  9:31               ` Yao Qi
2015-06-24 10:21 ` Several regressions and we branch soon Yao Qi
     [not found]   ` <87lhf8yz90.fsf@br87z6lw.de.ibm.com>
2015-06-25 13:34     ` Doug Evans
2015-06-25 18:00       ` Andreas Arnez
2015-06-30 15:21         ` Yao Qi
2015-06-30 18:09           ` Andreas Arnez
2015-07-01  8:01             ` Yao Qi
2015-07-10  9:33             ` Yao Qi
2015-07-10 16:12               ` Andreas Arnez
2015-07-10 16:23                 ` Ulrich Weigand [this message]
2015-07-20 15:08                   ` Andreas Arnez

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=20150710162332.182E6B042@oc7340732750.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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