public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gotom at debian dot or dot jp" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/205] math/bits/mathcalls.h contains empty macro arguments
Date: Sat, 05 Jun 2004 19:30:00 -0000	[thread overview]
Message-ID: <20040605193024.19650.qmail@sourceware.org> (raw)
In-Reply-To: <20040605132136.205.antoine.brodin@laposte.net>


------- Additional Comments From gotom at debian dot or dot jp  2004-06-05 19:30 -------
It's true that empty macro arguments is allowed in C99 firstly.
I guess this breaks some other compilers like tendra, but at 
the same time I wonder this type of macro is used for a long time.

I think to fix this problem is simply introduce the another define 
not to use empty macro arguments.  For example, define __MATHCALLF
does not use suffix and do:
   __MATHCALLF (acos, (_Mdouble_ __x));
instead of 
   __MATHCALL (acos,, (_Mdouble_ __x));
Andreas, is it sufficient?


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|gotom at debian dot or dot  |aj at suse dot de
                   |jp                          |
          Component|libc                        |math


http://sources.redhat.com/bugzilla/show_bug.cgi?id=205

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2004-06-05 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 13:21 [Bug libc/205] New: " antoine dot brodin at laposte dot net
2004-06-05 19:30 ` gotom at debian dot or dot jp [this message]
2004-06-07  8:00 ` [Bug math/205] " aj at suse dot de
2004-06-07  9:13 ` antoine dot brodin at laposte dot net
2004-08-10  2:04 ` drepper at redhat dot com

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=20040605193024.19650.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).