public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47295] New: libquadmath: List __complex128 and constants in the .texi file
Date: Fri, 14 Jan 2011 16:34:00 -0000	[thread overview]
Message-ID: <bug-47295-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47295

           Summary: libquadmath: List __complex128 and constants in the
                    .texi file
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


libquadmath.h contains a typedef and several macros (constants), which should
be listed in the documentation.

typedef _Complex float __attribute__((mode(TC))) __complex128;

// Macros
#define FLT128_MAX 1.18973149535723176508575932662800702e4932Q
#define FLT128_MIN 3.36210314311209350626267781732175260e-4932Q
#define FLT128_EPSILON 1.92592994438723585305597794258492732e-34Q
#define FLT128_DENORM_MIN 6.475175119438025110924438958227646552e-4966Q
#define FLT128_MANT_DIG 113
#define FLT128_MIN_EXP (-16381)
#define FLT128_MAX_EXP 16384
// TODO -- One day, we need to add the following macros:
// FLT128_DIG, FLT128_MIN_10_EXP, FLT128_MAX_10_EXP

#define HUGE_VALQ __builtin_huge_valq()


The math constants are added via
http://gcc.gnu.org/ml/gcc-patches/2011-01/msg00332.html

+#define M_Eq        2.7182818284590452353602874713526625Q  /* e */
+#define M_LOG2Eq    1.4426950408889634073599246810018921Q  /* log_2 e */
+#define M_LOG10Eq   0.4342944819032518276511289189166051Q  /* log_10 e */
+#define M_LN2q      0.6931471805599453094172321214581766Q  /* log_e 2 */
+#define M_LN10q     2.3025850929940456840179914546843642Q  /* log_e 10 */
+#define M_PIq       3.1415926535897932384626433832795029Q  /* pi */
+#define M_PI_2q     1.5707963267948966192313216916397514Q  /* pi/2 */
+#define M_PI_4q     0.7853981633974483096156608458198757Q  /* pi/4 */
+#define M_1_PIq     0.3183098861837906715377675267450287Q  /* 1/pi */
+#define M_2_PIq     0.6366197723675813430755350534900574Q  /* 2/pi */
+#define M_2_SQRTPIq 1.1283791670955125738961589031215452Q  /* 2/sqrt(pi) */
+#define M_SQRT2q    1.4142135623730950488016887242096981Q  /* sqrt(2) */
+#define M_SQRT1_2q  0.7071067811865475244008443621048490Q  /* 1/sqrt(2) */


             reply	other threads:[~2011-01-14 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 16:34 burnus at gcc dot gnu.org [this message]
2011-01-15  7:07 ` [Bug fortran/47295] " kargl at gcc dot gnu.org
2011-01-15 19:28 ` burnus at gcc dot gnu.org
2011-01-15 22:44 ` sgk at troutmask dot apl.washington.edu
2011-01-17 19:38 ` burnus at gcc dot gnu.org
2011-01-17 19:56 ` burnus at gcc dot gnu.org

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=bug-47295-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).