public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/15627] New: Testsuite failure: tst-xmmymm.out
Date: Fri, 14 Jun 2013 10:03:00 -0000	[thread overview]
Message-ID: <bug-15627-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15627

            Bug ID: 15627
           Summary: Testsuite failure: tst-xmmymm.out
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: siddhesh at redhat dot com

Description of problem:

tst-xmmymm fails with -O3 when built with gcc-4.8.  The reason seems to be that
the gcc-4.8 vectorizer (-ftree-vectorize enabled by default with -O3) manages
to vectorize instructions in memset.

=====tst-xmmymm.out=====
dl-minimal.os needed for __GI___assert_fail
dl-lookup.os needed for _dl_lookup_symbol_x
dl-profile.os needed for _dl_mcount_internal
dl-trampoline.os needed for _dl_x86_64_restore_sse
rtld-mmap.os needed for __mmap
dl-misc.os needed for _dl_dprintf
rtld-_exit.os needed for _exit
rtld-memcpy.os needed for memcpy
rtld-memset.os needed for memset
dl-scope.os needed for _dl_scope_free
dl-error.os needed for _dl_signal_cerror
rtld-stpcpy.os needed for stpcpy
rtld-strcmp.os needed for strcmp
rtld-strlen.os needed for strlen
rtld-fxstat.os needed for __GI___fxstat64
rtld-close.os needed for __close
rtld-write.os needed for __libc_write
rtld-llseek.os needed for __lseek
rtld-munmap.os needed for __munmap
rtld-open.os needed for __open
rtld-profil.os needed for __profil
rtld-prof-freq.os needed for __profile_frequency
rtld-memcmp.os needed for memcmp
rtld-getpid.os needed for __getpid
rtld-__longjmp.os needed for __longjmp
rtld-setjmp.os needed for __sigsetjmp
rtld-mempcpy.os needed for mempcpy
rtld-setitimer.os needed for __setitimer
rtld-sigaction.os needed for __sigaction
object files needed: dl-runtime.os dl-minimal.os dl-lookup.os dl-profile.os
dl-trampoline.os rtld-mmap.os dl-misc.os rtld-_exit.os rtld-memcpy.os
rtld-memset.os dl-scope.os dl-error.os rtld-stpcpy.os rtld-strcmp.os
rtld-strlen.os rtld-fxstat.os rtld-close.os rtld-write.os rtld-llseek.os
rtld-munmap.os rtld-open.os rtld-profil.os rtld-prof-freq.os rtld-memcmp.os
rtld-getpid.os rtld-__longjmp.os rtld-setjmp.os rtld-mempcpy.os
rtld-setitimer.os rtld-sigaction.os
function memset in rtld-memset.os modifies xmm/ymm
=====================

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-06-14 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 10:03 siddhesh at redhat dot com [this message]
2013-06-14 10:04 ` [Bug dynamic-link/15627] " siddhesh at redhat dot com
2013-06-14 18:45 ` siddhesh at redhat dot com
2014-06-13 15:05 ` fweimer at redhat 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-15627-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).