public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56866] gcc 4.7.x/gcc-4.8.x with '-O3 -march=bdver2' misscompiles glibc-2.17/crypt/sha512.c Date: Wed, 17 Apr 2013 21:49:00 -0000 [thread overview] Message-ID: <bug-56866-4-3f26U5ward@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56866-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56866 --- Comment #12 from Marc Glisse <glisse at gcc dot gnu.org> 2013-04-17 21:49:15 UTC --- (In reply to comment #11) > If fixing broken gcc's XOP/FMA/FMA4-extensions on AMD-CPUs depends on my > ability to extract a stand-alone-test from glibc-testsuite then I'm > realy sorry for not having the necessary skills (as already stated). Skills can be learned, and the best way is through practice. Ideally someone with the right combination of knowledge, hardware and free time would look at it, and you seem to be the closest currently ;-) > Why not simply using the failing test-cases from gcc-testsuite > which are all standalone and depends on XOP: Good idea. I suggest you pick a simple one: > +FAIL: gcc.target/i386/sse2-mul-1.c execution test it looks like a list of several tests in a row. If you can first replace the aborts with printf to determine the first one that fails, then remove everything after that point, you have already narrowed the issue quite a bit. Then you can try to simplify what remains. Ideally, you would get a program small enough that posting the dumps would show the obvious issue. Do make sure while reducing the program that it still works correctly without the bdver2 option.
next prev parent reply other threads:[~2013-04-17 21:49 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-07 16:53 [Bug c/56866] New: " winfried.magerl@t-online.de 2013-04-07 16:55 ` [Bug c/56866] " winfried.magerl@t-online.de 2013-04-09 13:47 ` [Bug target/56866] " rguenth at gcc dot gnu.org 2013-04-11 18:46 ` winfried.magerl@t-online.de 2013-04-11 19:36 ` ubizjak at gmail dot com 2013-04-11 21:07 ` winfried.magerl@t-online.de 2013-04-12 12:42 ` mikpe at it dot uu.se 2013-04-12 18:42 ` winfried.magerl@t-online.de 2013-04-14 15:55 ` mikpe at it dot uu.se 2013-04-17 18:41 ` winfried.magerl@t-online.de 2013-04-17 20:15 ` mikpe at it dot uu.se 2013-04-17 21:02 ` winfried.magerl@t-online.de 2013-04-17 21:49 ` glisse at gcc dot gnu.org [this message] 2013-04-24 20:58 ` winfried.magerl@t-online.de 2013-04-26 9:00 ` jakub at gcc dot gnu.org 2013-04-26 12:04 ` jakub at gcc dot gnu.org 2013-04-27 12:31 ` jakub at gcc dot gnu.org 2013-04-27 12:32 ` [Bug target/56866] [4.7/4.8/4.9 Regression] " jakub at gcc dot gnu.org 2013-04-29 16:08 ` winfried.magerl@t-online.de
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-56866-4-3f26U5ward@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).