public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64941] -O3 breaks tar Date: Thu, 05 Feb 2015 12:40:00 -0000 [thread overview] Message-ID: <bug-64941-4-wMhyK9XTB2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64941-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64941 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- First of all, -march=native and/or -mtune=native depends on the CPU you have, so it is very hard to reproduce without the same CPU. So, you should print what -march=native -mtune=native means for you, e.g. by adding -v to CFLAGS and pasting here the cc1 or cc1plus command line. Then, you could try to bisect it among the -O3 vs. -O2 *.o files, always take some -O3 and some -O2 files and find out the problematic one, attach preprocessed source for that one (others might have different version of glibc and its headers etc.).
next prev parent reply other threads:[~2015-02-05 12:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-05 5:22 [Bug c/64941] New: " brian at soulspark dot org 2015-02-05 5:28 ` [Bug c/64941] " brian at soulspark dot org 2015-02-05 5:37 ` [Bug target/64941] " pinskia at gcc dot gnu.org 2015-02-05 12:40 ` jakub at gcc dot gnu.org [this message] 2015-02-09 1:55 ` brian at soulspark dot org 2015-02-14 18:16 ` mikpelinux at gmail dot com 2015-02-14 19:58 ` brian at soulspark dot org 2015-02-15 1:21 ` hjl.tools at gmail dot com 2015-02-15 4:16 ` hjl.tools at gmail dot com 2015-02-15 14:06 ` hjl.tools 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-64941-4-wMhyK9XTB2@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).