This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/40766] this fortran program is too slow
- From: "maxim at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 May 2010 10:46:08 -0000
- Subject: [Bug fortran/40766] this fortran program is too slow
- References: <bug-40766-15353@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #20 from mkuvyrkov at gcc dot gnu dot org 2010-05-10 10:46 -------
Subject: Re: this fortran program is too slow
On 5/7/10 1:38 AM, steven at gcc dot gnu dot org wrote:
> ------- Comment #19 from steven at gcc dot gnu dot org 2010-05-06 21:38 -------
> One possibility is to see if the glibc patches for this issue can be merged
> into eglibc... Maxim what do you think?
I'll look into this when I have a minute.
I'm hesitant to merging patches to EGLIBC that were not submitted to
either GLIBC or EGLIBC mailing lists. There are copyright assignment
issues with extracting patches from (open)SUSE's GLIBC and committing
them in to EGLIBC. Copyright assignment is not an absolutely blocking
issue, but it is one of the concerns.
The plan of action is to find out who the author of the patch is and ask
him or her to submit the patch to EGLIBC.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40766