diff options
| author | vonPalitroque | 2017-07-26 15:39:22 -0400 |
|---|---|---|
| committer | vonPalitroque | 2017-07-26 15:39:22 -0400 |
| commit | a50f4d5a9cd14b31b23f1e9d0453c29db9742f36 (patch) | |
| tree | 2766f2eaa88e73a9fa01c8713f06e7823827b67e /fix-insn-delay_cycles_32x.patch | |
| parent | fb932226aef4d9a956af72bdbd2f64d61f3ac76e (diff) | |
| download | aur-a50f4d5a9cd14b31b23f1e9d0453c29db9742f36.tar.gz | |
Updated to latest version.
Updated to latest upstream version. Small caveat:
The bug described in pr79242 is still not resolved and activity on it seems to
be of low interest. Unfortunately, I do not have the time to look into it that
much. As such, instead of delaying the update until the bug is resolved, I have
opted to instead revert the change that exposed the bug [2]. Yes, this means
that the bug is still there and may be triggered a different way, I have yet to
find a scenario where it happens though.
I will ask then the community: if such case is found, please let me know and/or
add it to [1]. I will then prepare and release a PKGBUILD based on gcc 6.4
instead.
Cheers,
Orlando.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79242
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71289
Diffstat (limited to 'fix-insn-delay_cycles_32x.patch')
0 files changed, 0 insertions, 0 deletions