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/46625] New: libquadmath: Mangle internal symbols; rename __float128 <-> string functions
Date: Tue, 23 Nov 2010 18:41:00 -0000	[thread overview]
Message-ID: <bug-46625-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: libquadmath: Mangle internal symbols; rename
                    __float128 <-> string functions
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


For libquadmath.a it makes sense to mangle non-exported symbols, e.g. by
prefixing them with __quadmath_

quadmath_strtopQ and quadmath_dtoaq look ugly, Jakub suggests:
   quadmath_strtoq and quadmath_qtostr


C example (to have one somewhere):

/* Compile with  gcc test.c -lquadmath -lm  shows:
:+1.41421356237309504880e+00:
:+1.2345678000e-05:
*/

#include <quadmath.h>
#include <stdio.h>

int main()
{
  __float128 r;
  char str[200];

  r = 2.0q;
  r = sqrtq(r);
  quadmath_dtoaq (str, 200, 20, r);
  printf(":%s:\n", str);

  quadmath_strtopQ ("1.2345678", NULL, &r);
  r = r/100000.0q;
  quadmath_dtoaq (str, 200, 10, r);
  printf(":%s:\n", str);

  return 0;
}


             reply	other threads:[~2010-11-23 18:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 18:41 burnus at gcc dot gnu.org [this message]
2010-12-01 12:47 ` [Bug fortran/46625] " burnus at gcc dot gnu.org
2010-12-03  8:44 ` burnus at gcc dot gnu.org
2010-12-08 22:43 ` burnus at gcc dot gnu.org
2010-12-11 17:48 ` burnus at gcc dot gnu.org
2010-12-13 19:45 ` burnus at gcc dot gnu.org
2010-12-13 19:59 ` burnus at gcc dot gnu.org
2011-01-16 17:16 ` jakub 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-46625-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).