Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] avoid 'gamma' function name
Date: Mon, 08 Sep 2003 21:14:00 -0000	[thread overview]
Message-ID: <20030908211403.GA26925@nevyn.them.org> (raw)
In-Reply-To: <200309082111.h88LBvq6011543@duracef.shout.net>

On Mon, Sep 08, 2003 at 05:11:57PM -0400, Michael Elizabeth Chastain wrote:
> This patchlet works around a recent change in gcc HEAD where 'gamma' is
> now a reserved identifier, even when 'math.h' is not included.
> 
> I've reported this as a regression bug against gcc:
> 
>   http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12213
>   [3.4 regression] warning: conflicting types for builtin-function 'gamma'
> 
> I'm pretty sure this is actually a bug in gcc.  A draft of the C9x spec
> says that all external library names are reserved, and does not qualify
> that by saying that the header file for that name has to be included.
> However, the particular name 'gamma' is an obsolete name and not
> mentioned in the standard.
> 
> However -- the purpose of gdb1250.exp is to test backtracing and
> prologue analysis.  It's not to test C library reserved identifiers.
> So this patch just avoids the issue.
> 
> Testing: tested on native i686-pc-linux-gnu, gcc v2 and v3, dwarf-2 and
> stabs+.  Specifically tested with gcc HEAD that thinks 'gamma' is
> a reserved identifier.
> 
> Okay to commit?

Sounds reasonable to me.  I'm 99.9% sure you're right about the GCC
bug, too - at least if gcc HEAD defaults to gnu99 mode?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-09-08 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 21:11 Michael Elizabeth Chastain
2003-09-08 21:14 ` Daniel Jacobowitz [this message]
2003-09-08 21:29 Michael Elizabeth Chastain
2003-09-08 21:31 Michael Elizabeth Chastain

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=20030908211403.GA26925@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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