Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: davem@davemloft.net (David Miller)
Cc: gdb-patches@sourceware.org, kettenis@gnu.org
Subject: Re: [PATCH] Allow struct 'return' on 32-bit sparc.
Date: Fri, 08 Feb 2013 18:17:00 -0000	[thread overview]
Message-ID: <201302081816.r18IGd4s006087@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20130201.161300.1158114789368969492.davem@davemloft.net> from "David Miller" at Feb 01, 2013 04:13:00 PM

David Miller wrote:

>  void
>  return_command (char *retval_exp, int from_tty)
>  {
> +  enum return_value_convention rv_conv;
>    struct frame_info *thisframe;
>    struct gdbarch *gdbarch;
>    struct symbol *thisfun;

This gives me:

cc1: warnings being treated as errors
/home/kwerner/dailybuild/spu-tc-2013-02-08/gdb-head/src/gdb/stack.c: In function 'return_command':
/home/kwerner/dailybuild/spu-tc-2013-02-08/gdb-head/src/gdb/stack.c:2281: warning: 'rv_conv' may be used uninitialized in this function

when building with GCC 4.1.2 (as of RHEL5).

> @@ -2327,6 +2328,7 @@ return_command (char *retval_exp, int from_tty)
>        if (thisfun != NULL)
>  	function = read_var_value (thisfun, thisframe);
>  
> +      rv_conv = RETURN_VALUE_REGISTER_CONVENTION;
>        if (TYPE_CODE (return_type) == TYPE_CODE_VOID)
>  	/* If the return-type is "void", don't try to find the
>             return-value's location.  However, do still evaluate the

Maybe just move this up to the definition?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2013-02-08 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 21:13 David Miller
2013-02-04 23:57 ` Mark Kettenis
2013-02-05  1:03   ` David Miller
2013-02-05 20:19     ` Mark Kettenis
2013-02-05 20:31       ` David Miller
2013-02-06 19:41     ` David Miller
2013-02-08 18:17 ` Ulrich Weigand [this message]
2013-02-08 19:10   ` David Miller
2013-02-08 19:13     ` David Miller

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=201302081816.r18IGd4s006087@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=gdb-patches@sourceware.org \
    --cc=kettenis@gnu.org \
    /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