public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53726] [4.8 Regression] aes test performance drop for eembc_2_0_peak_32
Date: Wed, 20 Jun 2012 14:55:00 -0000	[thread overview]
Message-ID: <bug-53726-4-Sy3W4K9ltE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53726-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from rguenther at suse dot de <rguenther at suse dot de> 2012-06-20 14:53:58 UTC ---
On Wed, 20 Jun 2012, hjl.tools at gmail dot com wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53726
> 
> --- Comment #12 from H.J. Lu <hjl.tools at gmail dot com> 2012-06-20 14:43:11 UTC ---
> (In reply to comment #11)
> > (In reply to comment #9)
> > > (In reply to comment #3)
> > > > I added executable testcase. Command line to compile
> > > > 
> > > > gcc -g -ansi -O3 -ffast-math -msse2 -mfpmath=sse -m32 -static  -march=corei7
> > > > -mtune=corei7   test.c m.c
> > > > 
> > > 
> > > Please compare results without -static.
> > 
> > Same results.  memcpy ends up here:
> > 
> > 
> > this seems to be sysdeps/i386/i586/memcpy.S
> 
> Your libc.so doesn't support IFUNC optimization.

Quite possible (for whatever reason).


  parent reply	other threads:[~2012-06-20 14:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  6:10 [Bug c/53726] New: " vbyakovl23 at gmail dot com
2012-06-20  6:13 ` [Bug c/53726] " vbyakovl23 at gmail dot com
2012-06-20  9:28 ` [Bug tree-optimization/53726] " rguenth at gcc dot gnu.org
2012-06-20 10:48 ` vbyakovl23 at gmail dot com
2012-06-20 10:50 ` vbyakovl23 at gmail dot com
2012-06-20 11:48 ` rguenth at gcc dot gnu.org
2012-06-20 12:31 ` rguenth at gcc dot gnu.org
2012-06-20 12:47 ` hjl.tools at gmail dot com
2012-06-20 13:30 ` rguenther at suse dot de
2012-06-20 14:20 ` hjl.tools at gmail dot com
2012-06-20 14:35 ` vbyakovl23 at gmail dot com
2012-06-20 14:36 ` rguenth at gcc dot gnu.org
2012-06-20 14:44 ` hjl.tools at gmail dot com
2012-06-20 14:47 ` hjl.tools at gmail dot com
2012-06-20 14:52 ` hjl.tools at gmail dot com
2012-06-20 14:55 ` rguenther at suse dot de [this message]
2012-06-20 15:10 ` rguenth at gcc dot gnu.org
2012-06-20 15:37 ` hjl.tools at gmail dot com
2012-06-21  8:47 ` rguenther at suse dot de
2012-06-21 12:47 ` vbyakovl23 at gmail dot com
2012-06-21 12:51 ` hjl.tools at gmail dot com
2012-06-21 12:56 ` hjl.tools at gmail dot com
2012-06-22 22:46 ` hubicka at ucw dot cz
2012-06-22 23:04   ` Jan Hubicka
2012-06-22 23:05 ` hubicka at ucw dot cz

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-53726-4-Sy3W4K9ltE@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).