public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebastiano.vigna at unimi dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66348] Simple loop never exits with -O1, exits with -O0 Date: Sat, 06 Jun 2015 23:38:00 -0000 [thread overview] Message-ID: <bug-66348-4-yKQLX9svTB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66348-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66348 --- Comment #12 from Sebastiano Vigna <sebastiano.vigna at unimi dot it> --- BTW, to further restrict the search I'm trying to replicate the bug with -fsanitize=address, or at least to get to the problematic call under -fsanitize=address, but it'll take a while. I have to recompile the gcc suite, as the current version of libasan does not allocate more than 64GB (in Fedora, libasan is built with gcc).
next prev parent reply other threads:[~2015-06-06 23:38 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-30 22:22 [Bug c/66348] New: Simple loop with 64-bit index has only lower half initialized correctly sebastiano.vigna at unimi dot it 2015-05-30 22:46 ` [Bug c/66348] Simple loop has only lower half of the 64-bit counter " pinskia at gcc dot gnu.org 2015-05-30 23:00 ` sebastiano.vigna at unimi dot it 2015-05-30 23:01 ` sebastiano.vigna at unimi dot it 2015-06-01 8:19 ` rguenth at gcc dot gnu.org 2015-06-02 7:21 ` sebastiano.vigna at unimi dot it 2015-06-02 7:23 ` sebastiano.vigna at unimi dot it 2015-06-05 14:33 ` sebastiano.vigna at unimi dot it 2015-06-05 15:28 ` ubizjak at gmail dot com 2015-06-05 20:46 ` [Bug c/66348] Simple loop never exit with -O1, exits with -O0 sebastiano.vigna at unimi dot it 2015-06-05 22:14 ` [Bug c/66348] Simple loop never exits " miyuki at gcc dot gnu.org 2015-06-06 23:33 ` sebastiano.vigna at unimi dot it 2015-06-06 23:38 ` sebastiano.vigna at unimi dot it [this message] 2021-11-29 8:56 ` [Bug middle-end/66348] " sebastiano.vigna at unimi dot it
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-66348-4-yKQLX9svTB@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).