public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40766] this fortran program is too slow
Date: Tue, 24 Apr 2012 13:14:00 -0000	[thread overview]
Message-ID: <bug-40766-4-N8nvvchXmg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40766-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #23 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-04-24 13:13:13 UTC ---
The glibc libm work has mainly been oriented at correctness rather than 
performance, and postdates the 2.15 release so will be new in 2.16 (the 
2.15 announcement came some time after the actual tag and branching).


  parent reply	other threads:[~2012-04-24 13:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40766-4@http.gcc.gnu.org/bugzilla/>
2011-07-24 18:50 ` dfranke at gcc dot gnu.org
2012-04-19 14:37 ` jb at gcc dot gnu.org
2012-04-24 13:14 ` joseph at codesourcery dot com [this message]
2013-06-19 12:51 ` [Bug tree-optimization/40766] " dominiq at lps dot ens.fr
2009-07-15 15:33 [Bug fortran/40766] New: " linuxl4 at sohu dot com
2009-07-15 15:49 ` [Bug fortran/40766] " linuxl4 at sohu dot com
2009-07-15 15:56 ` pinskia at gcc dot gnu dot org
2009-07-15 17:59 ` ubizjak at gmail dot com
2009-07-15 18:35 ` linuxl4 at sohu dot com
2009-07-15 18:51 ` dominiq at lps dot ens dot fr
2009-07-15 20:27 ` burnus at gcc dot gnu dot org
2009-07-15 21:01 ` rguenth at gcc dot gnu dot org
2009-07-16  4:37 ` linuxl4 at sohu dot com
2009-07-16  5:06 ` kargl at gcc dot gnu dot org
2009-07-16  6:56 ` ubizjak at gmail dot com
2009-07-16  7:17 ` ubizjak at gmail dot com
2009-07-16  9:07 ` rguenth at gcc dot gnu dot org
2009-07-16  9:43 ` burnus at gcc dot gnu dot org
2009-07-16 10:06 ` ubizjak at gmail dot com
2009-07-22 11:15 ` eres at il dot ibm dot com
2009-07-25  7:40 ` linuxl4 at sohu dot com
2009-12-05  6:29 ` jvdelisle at gcc dot gnu dot org
2009-12-05 19:01 ` burnus at gcc dot gnu dot org
2010-05-06 19:23 ` dfranke at gcc dot gnu dot org
2010-05-06 21:38 ` steven at gcc dot gnu dot org
2010-05-10 10:46 ` maxim at codesourcery 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=bug-40766-4-N8nvvchXmg@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).