public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67531] No IEEE rounding support for powerpc long double type
Date: Fri, 11 Sep 2015 13:50:00 -0000	[thread overview]
Message-ID: <bug-67531-4-cjFRgqGzss@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67531-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67531

--- Comment #5 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
(In reply to Francois-Xavier Coudert from comment #3)
> How about with this? I'm trying to come as close as possible to the exact
> sequence of fe.etround() calls as the Fortran front-end and runtime library
> would end up performing…
> 
> 
> #include <fenv.h>
> #include <stdio.h>
> 
> int main (void)
> {
>   int r;
>   long double x1, x2, x;
> 
>   x1 = 1;
>   x = 3;
>   r = fegetround ();
>   fesetround (FE_UPWARD);
>   x1 = x1 / x;
>   fesetround (r);
> 
>   x2 = 1;
>   x = 3;
>   r = fegetround ();
>   fesetround (FE_DOWNWARD);
>   x2 = x2 / x;
>   fesetround (r);
> 
>   printf ("%.40Lg\n", x1);
>   printf ("%.40Lg\n", x2);
> }

pthaugen@genoa:~$ ~/install/gcc/trunk/bin/gcc junk.c -lm && ./a.out
0.3333333333333333333333333333333353876586
0.3333333333333333333333333333333292246828
>From gcc-bugs-return-496981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 11 13:51:00 2015
Return-Path: <gcc-bugs-return-496981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10448 invoked by alias); 11 Sep 2015 13:51:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10181 invoked by uid 48); 11 Sep 2015 13:50:57 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59478] Optimize variable access via byte copy
Date: Fri, 11 Sep 2015 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59478-4-hlpQWivXDr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00959.txt.bz2
Content-length: 1053

https://gcc.gnu.org/bugzilla/show_bug.cgi?idY478

--- Comment #1 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Oleg Endo from comment #0)
> This happens at least on SH with trunk rev 205905 (4.9).
> I'm not sure whether these are target specific or not.
>
> Accessing float values as integers can be done in various ways.  One way is
> to do a byte copy...
>
> int float_as_int (float val)
> {
>   char valbytes[sizeof (float)];
>   __builtin_memcpy (valbytes, &val, sizeof (float));
>
>   int result;
>   __builtin_memcpy (&result, valbytes, sizeof (float));
>
>   return result;
> }
>
> The above compiled with -m4-single -ml -O2 results in:
>
>         add     #-8,r15
>         fmov.s  fr5,@r15
>         mov.l   @r15,r0
>         rts
>         add     #8,r15
>
> which is not so bad actually, but could be done better by utilizing the fpul
> register, as it is done when using the union approach:

This case got better.  It now produces the expected sequence:

        flds    fr5,fpul
        rts
        sts     fpul,r0


  parent reply	other threads:[~2015-09-11 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 22:09 [Bug fortran/67531] New: FAIL: gfortran.dg/ieee/large_2.f90 -O0 execution test pthaugen at gcc dot gnu.org
2015-09-10 21:31 ` [Bug fortran/67531] " pthaugen at gcc dot gnu.org
2015-09-10 21:45 ` fxcoudert at gcc dot gnu.org
2015-09-10 22:00 ` schwab@linux-m68k.org
2015-09-11 13:50 ` pthaugen at gcc dot gnu.org [this message]
2021-05-04 12:31 ` [Bug fortran/67531] No IEEE rounding support for powerpc long double type rguenth 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-67531-4-cjFRgqGzss@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).