Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: kettenis@chello.nl, gcc@gcc.gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix PR gdb/290
Date: Sat, 09 Feb 2002 11:19:00 -0000	[thread overview]
Message-ID: <3C657641.1080906@cygnus.com> (raw)
In-Reply-To: <20020209172736.38606.qmail@elgar.kettenis.dyndns.org>

[added gcc]


> Checked in as obvious.  Wonder why GCC didn't warn about this.  Should
> we add some more -Wxxx flags?


I was looking at it and wondering the same thing - I know I've fixed 
botched return type warnings.  Trying:

static int f1 (void) { return 1; }
static void f2 (void) { return 1; }
static void f3 (void) { return; }
static int f4 (void) { return; }

I get:

-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses 
-Wpointer-arith -Wuninitialized -Werror
doublest.c: In function `f2':
doublest.c:741: warning: `return' with a value, in function returning void
doublest.c: In function `f4':
doublest.c:743: warning: `return' with no value, in function returning 
non-void

so ok so far.  Hmm, I think this tells the story:

static void f5 (int a) { return f3(); }

Returning the result from a function that returns void (f3()) doesn't 
attract a warning.

Bug or feature?

	Andrew


> Mark
> 
> 
> Index: ChangeLog
> from  Mark Kettenis  <kettenis@gnu.org>
> 
> * doublest.c (store_typed_floating): Don't try to return a value.
> 	Fixes PR gdb/290.
> 
> Index: doublest.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/doublest.c,v
> retrieving revision 1.8
> diff -u -p -r1.8 doublest.c
> --- doublest.c 2002/01/22 19:57:40 1.8
> +++ doublest.c 2002/02/09 17:24:44
> @@ -732,9 +732,9 @@ store_typed_floating (void *addr, const 
>    memset (addr, 0, TYPE_LENGTH (type));
>  
>    if (TYPE_FLOATFORMAT (type) == NULL)
> -    return store_floating (addr, TYPE_LENGTH (type), val);
> -
> -  floatformat_from_doublest (TYPE_FLOATFORMAT (type), &val, addr);
> +    store_floating (addr, TYPE_LENGTH (type), val);
> +  else
> +    floatformat_from_doublest (TYPE_FLOATFORMAT (type), &val, addr);
>  }
>  
>  /* Convert a floating-point number of type FROM_TYPE from a
> 
> 



  reply	other threads:[~2002-02-09 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09  9:27 kettenis
2002-02-09 11:19 ` Andrew Cagney [this message]
2002-02-09 11:37   ` Joe Buck
2002-02-09 11:51     ` Andrew Cagney
2002-02-09 12:18     ` Andreas Schwab
2002-02-09 17:39       ` Joe Buck

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=3C657641.1080906@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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