public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamrial at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/67920] wrong code with -O3
Date: Sat, 10 Oct 2015 21:00:00 -0000 [thread overview]
Message-ID: <bug-67920-4-J55Uge5Gd6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67920-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67920
--- Comment #3 from James Almer <jamrial at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> Can you also compile with -fsanitize=undefined and try that? Can you also
> try -fsanitize=address ?
>
> This might detect if it is a bug in the code vs a bug in GCC.
Can't check with gcc 6 because of pr67921, but asan/ubsan in gcc 5.2.0 and
clang 3.1 apparently don't complain about the code.
ubsan gcc 5.2.0:
http://fate.ffmpeg.org/report.cgi?time=20151010033356&slot=x86_64-archlinux-gcc-ubsan
asan gcc 5.2.0:
http://fate.ffmpeg.org/report.cgi?time=20151010181435&slot=x86_64-archlinux-gcc-asan
Clang 3.1 asan:
http://fate.ffmpeg.org/report.cgi?time=20151010171909&slot=x86_64-debian-asan-144800
next prev parent reply other threads:[~2015-10-10 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 19:46 [Bug rtl-optimization/67920] New: " jamrial at gmail dot com
2015-10-10 20:01 ` [Bug rtl-optimization/67920] " jamrial at gmail dot com
2015-10-10 20:08 ` pinskia at gcc dot gnu.org
2015-10-10 21:00 ` jamrial at gmail dot com [this message]
2015-10-12 7:43 ` [Bug rtl-optimization/67920] [6 Regression] " rguenth at gcc dot gnu.org
2015-10-13 0:17 ` [Bug tree-optimization/67920] " jamrial at gmail dot com
2015-10-13 0:18 ` jamrial at gmail dot com
2015-10-13 10:43 ` mpolacek at gcc dot gnu.org
2015-10-13 13:11 ` ysrumyan at gmail dot com
2015-10-13 17:00 ` jamrial 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-67920-4-J55Uge5Gd6@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: link
Be 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).