public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/35729] const volatile variable access incorrectly hoisted out of loop Date: Sun, 25 May 2008 18:04:00 -0000 [thread overview] Message-ID: <20080525180321.23173.qmail@sourceware.org> (raw) In-Reply-To: <bug-35729-12544@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from ghazi at gcc dot gnu dot org 2008-05-25 18:03 ------- The testcase also fails for me on x86_64-unknown-linux-gnu or i686-unknown-linux-gnu but requires -fpic/-fPIC to trigger. (That may explain the darwin x86 error.) See: x86_64: http://gcc.gnu.org/ml/gcc-testresults/2008-05/msg02221.html i686: http://gcc.gnu.org/ml/gcc-testresults/2008-05/msg01800.html -- ghazi at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ghazi at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35729
next prev parent reply other threads:[~2008-05-25 18:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-28 3:05 [Bug c/35729] New: const volatile variable accessed that should not be regehr at cs dot utah dot edu 2008-03-28 10:27 ` [Bug rtl-optimization/35729] const volatile variable access incorrectly hoisted out of loop rguenth at gcc dot gnu dot org 2008-03-30 15:02 ` rakdver at gcc dot gnu dot org 2008-03-31 14:21 ` rakdver at gcc dot gnu dot org 2008-04-01 9:40 ` dominiq at lps dot ens dot fr 2008-04-01 10:28 ` dominiq at lps dot ens dot fr 2008-04-27 17:18 ` danglin at gcc dot gnu dot org 2008-05-25 18:04 ` ghazi at gcc dot gnu dot org [this message] 2008-10-16 21:34 ` sje at cup dot hp dot com 2008-11-08 1:36 ` danglin at gcc dot gnu dot org 2008-11-08 20:20 ` ebotcazou at gcc dot gnu dot org 2008-12-02 14:22 ` krebbel at gcc dot gnu dot org 2009-01-05 23:15 ` sje at cup dot hp dot com 2009-01-17 2:50 ` ghazi at gcc dot gnu dot org 2009-01-19 18:53 ` ubizjak at gmail dot com 2009-11-29 16:22 ` ghazi at gcc dot gnu dot org 2009-11-29 16:38 ` rguenth at gcc dot gnu dot org
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=20080525180321.23173.qmail@sourceware.org \ --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).