From: James Cloos <cloos@jhcloos.com>
To: Rich Felker <dalias@libc.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
musl@lists.openwall.com
Subject: Re: Broken GCC versions: 4.8.2 and 4.9.0
Date: Sun, 11 May 2014 16:08:37 -0400 [thread overview]
Message-ID: <m3vbtc5b8h.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <20140511190320.GV26358@brightrain.aerifal.cx> (Rich Felker's message of "Sun, 11 May 2014 15:03:20 -0400")
>>>>> "RF" == Rich Felker <dalias@libc.org> writes:
RF> I've tested it on gcc.godbolt.org and others have tested with local
RF> gcc 4.8.2 and 4.9.0, probably distro-provided (I didn't ask).
I just tried debian-sid's 4.9. That does show the bug. As does their
gcc-snapshot version (a 4.10 pre).
Perhaps the distro(s) which have the bug with 4.8.2 backported the commit
where the bug first occurs?
RF> I wonder if the broken GCC is using isl/cloog
I use the graphite optimizer on my Gentoo box (which generated the
assembly I quoted). The graphite code is only used when one or more
of -floop-interchange -floop-strip-mine -floop-block are specified.
Testing with those options doesn't change the results.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2014-05-11 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 1:05 Rich Felker
2014-05-11 16:10 ` Thomas Petazzoni
2014-05-11 16:19 ` Rich Felker
2014-05-11 18:46 ` James Cloos
2014-05-11 19:03 ` Rich Felker
2014-05-11 20:08 ` James Cloos [this message]
2014-05-11 21:20 ` Rich Felker
2014-05-12 1:23 ` Stephen Thomas
2014-05-12 9:28 ` Natanael Copa
2014-05-12 14:30 ` Anthony G. Basile
2014-05-14 7:49 ` Natanael Copa
2014-05-12 12:13 ` Rich Felker
2014-05-12 13:49 ` Thorsten Glaser
2014-05-12 13:56 ` James Cloos
2014-05-11 20:20 ` Matias A. Fonzo
2014-05-15 4:45 ` Rich Felker
2014-05-19 0:47 ` Rich Felker
2014-05-19 11:47 ` Szabolcs Nagy
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=m3vbtc5b8h.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=thomas.petazzoni@free-electrons.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).