git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] Remove noreturn function pointers in usage.c

From
Jeff King <peff@peff.net>
Date
Jun 9, 2011, 05:52 UTC
Message-ID
<20110609055224.GA27780@sigill.intra.peff.net>
In-Reply-To
<20110609045915.GA15448@one.firstfloor.org>
On Thu, Jun 09, 2011 at 06:59:15AM +0200, Andi Kleen wrote:
Show 6 quoted lines
> >  - Potential impact to people who do not use Gcc 4.6 with profile feedback
> >    is not explained away well, except for "Doesn't seem to make any
> >    difference."
> 
> I merely went by "there are no new warnings" (I assume that's the main
> motivation)
On your compiler and settings, perhaps. With your patch I get:
  usage.c: In function ‘die’:
  usage.c:70:1: error: ‘noreturn’ function does return [-Werror]
And rightfully so:
void NORETURN die(const char *err, ...)
{
        va_list params;
        va_start(params, err);
        die_routine(err, params);
        va_end(params);
}

You've stripped the NORETURN from die_routine, so of course it looks like we end up returning.

This is with:
  $ gcc --version | head -n 1
  gcc (Debian 4.6.0-11) 4.6.1 20110604 (prerelease)
-Peff
Previous: Andi KleenNext: Andi Kleen
Message 5 of 7 in “Remove noreturn function pointers in usage.c”
  1. 1/2 Remove noreturn function pointers in usage.cAndi Kleen, Jun 8, 2011
  2. 2/2 Add profile feedback build to gitAndi Kleen, Jun 8, 2011
  3. Junio C HamanoJun 9, 2011
  4. Andi KleenJun 9, 2011
  5. Jeff KingJun 9, 2011
  6. Andi KleenJun 9, 2011
  7. Erik Faye-LundJun 9, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.