public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "talebi.hossein at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/52537] New: slow trim function Date: Fri, 09 Mar 2012 08:48:00 -0000 [thread overview] Message-ID: <bug-52537-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52537 Bug #: 52537 Summary: slow trim function Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libfortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: talebi.hossein@gmail.com Hello, The trim function in Gfortran seems to be a a lot slower than the intel compiler. Sometimes I have to read some input text files which can very large(1.5GB); Comparing the intel and gfortran, the gfortran takes 150 seconds where intel spends only 50 seconds. I checked, and there seems to a large time spend on the trim function. I am not sure if intel does some other optimization but I never got such huge performance difference between gfortran and ifort. Thank you.
next reply other threads:[~2012-03-09 8:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-09 8:48 talebi.hossein at gmail dot com [this message] 2012-03-09 9:14 ` [Bug libfortran/52537] " burnus at gcc dot gnu.org 2012-03-11 7:51 ` tkoenig at gcc dot gnu.org 2012-03-11 17:19 ` tkoenig at gcc dot gnu.org 2012-03-11 17:28 ` talebi.hossein at gmail dot com 2012-04-12 10:47 ` tkoenig at gcc dot gnu.org 2012-05-11 14:16 ` tkoenig at gcc dot gnu.org 2012-05-11 19:06 ` tkoenig at gcc dot gnu.org 2012-05-11 19:17 ` tkoenig at gcc dot gnu.org 2012-06-07 14:51 ` tkoenig at gcc dot gnu.org 2012-06-07 16:03 ` talebi.hossein at gmail 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-52537-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: linkBe 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).