public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50588] gcc produce bad inlined code with -march=athlon -O2 Date: Sun, 02 Oct 2011 18:56:00 -0000 [thread overview] Message-ID: <bug-50588-4-jEXOElfzfs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50588-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50588 --- Comment #4 from Mikael Pettersson <mikpe at it dot uu.se> 2011-10-02 18:55:45 UTC --- The failure started with r164552: http://gcc.gnu.org/ml/gcc-cvs/2010-09/msg00849.html It's enough to pass -O2 -mtune=athlon to trigger the bug, you don't need -march. I don't see anything x86-specific in that revision so quite possibly it's just triggering a latent x86 backend error.
next prev parent reply other threads:[~2011-10-02 18:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-02 11:40 [Bug target/50588] New: " newsgrp at duradsl dot dyndns.org 2011-10-02 11:58 ` [Bug target/50588] " mikpe at it dot uu.se 2011-10-02 11:59 ` newsgrp at duradsl dot dyndns.org 2011-10-02 13:01 ` mikpe at it dot uu.se 2011-10-02 18:56 ` mikpe at it dot uu.se [this message] 2011-10-02 20:36 ` pinskia at gcc dot gnu.org 2011-10-02 20:45 ` mikpe at it dot uu.se 2011-10-02 22:00 ` newsgrp at duradsl dot dyndns.org 2011-10-02 22:01 ` newsgrp at duradsl dot dyndns.org 2011-10-02 22:40 ` newsgrp at duradsl dot dyndns.org 2011-10-03 8:36 ` mikpe at it dot uu.se 2011-10-03 11:46 ` mikpe at it dot uu.se 2011-10-03 12:57 ` mikpe at it dot uu.se 2011-10-03 19:28 ` mikpe at it dot uu.se 2011-10-06 13:30 ` bernds at gcc dot gnu.org 2011-12-18 14:12 ` mikpe at it dot uu.se 2011-12-31 23:08 ` [Bug rtl-optimization/50588] " pinskia at gcc dot gnu.org 2012-01-01 9:25 ` [Bug rtl-optimization/50588] gcc produce incorrect " ebotcazou at gcc dot gnu.org 2014-05-18 19:03 ` mikpelinux 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-50588-4-jEXOElfzfs@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).