** Changed in: gcc
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Fixed for GCC 10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status in gcc:
Fix Released
Status in gcc-9
GCC 9.4 is being released, retargeting bugs to GCC 9.5.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status
Fixed everywhere.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status in gcc:
Confirmed
Status in gcc-9
The releases/gcc-9 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:066184a282b622ac6880150eb4e42fe57881b606
commit r9-8269-g066184a282b622ac6880150eb4e42fe57881b606
Author: Peter Bergner
Date: Sun Feb 23 18:22:57 2020 -0600
rs6000: Fix infinite loop building ghostscript
GCC 9.3.0 has been released, adjusting target milestone.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status
The fixes have been reverted for 9.3/8.4.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status in gcc:
The releases/gcc-8 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:53efbfe030a5fda41e5e7856d76ea827dd09f49c
commit r8-10050-g53efbfe030a5fda41e5e7856d76ea827dd09f49c
Author: Peter Bergner
Date: Sun Feb 23 22:04:44 2020 -0600
rs6000: Fix infinite loop building ghostscript
Simple backports to GCC 8 and 9 exposed some bugs that have already been
fixed on trunk. The following patch resubmission includes those extra
fixes that need backports too:
https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01253.html
--
You received this bug notification because you are a
Caused PR93974.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status in gcc:
Confirmed
Status in gcc-9
** Changed in: gcc
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
reverted the work-around in ghostscript
** Changed in: ghostscript (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
This bug was fixed in the package gcc-9 - 9.2.1-29ubuntu1
---
gcc-9 (9.2.1-29ubuntu1) focal; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
- Disable the LTO build on arm64, armhf for now, takes 24+ hours ...
gcc-9 (9.2.1-29)
** Changed in: gcc
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Ok, after debugging, this looks to be a bug in rs6000_legitimate_address_p().
At the beginning of LRA, we have the following insn:
(insn 520 67 71 5 (set (mem:V16QI (and:DI (reg/f:DI 110 sfp)
(const_int -16 [0xfff0])) [0 MEM
[(char *) + 16B]+0 S16 A128])
The master branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:b82d426662469ee8b78ec7e8f74abe950485c9d5
commit r10-6760-gb82d426662469ee8b78ec7e8f74abe950485c9d5
Author: Peter Bergner
Date: Thu Feb 20 11:08:02 2020 -0600
rs6000: Fix infinite loop building ghostscript and icu
The master branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:e6f24f824beb8ba6805702e287bbd6153b472488
commit r10-6762-ge6f24f824beb8ba6805702e287bbd6153b472488
Author: Peter Bergner
Date: Thu Feb 20 11:25:12 2020 -0600
rs6000: Fix infinite loop building ghostscript and icu
this is only *worked around* in ghostscript, not fixed.
** Changed in: ghostscript (Ubuntu)
Status: Fix Released => Confirmed
** Also affects: gcc-9 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gcc (Ubuntu)
--
You received this bug notification because
** Changed in: gcc
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck (or extremely slow) on ppc64el
Status in
(In reply to Jakub Jelinek from comment #8)
> On the #c7 testcase, this started with
> r8-6072-ga3a821c903c9fa2288712d31da2038d0297babcb (so I wonder why this
> isn't a 8/9/10 Regression).
I'm not sure Kelvin's patch is to blame. I think it's just exposing a
latent issue.
--
You received this
On the #c7 testcase, this started with
r8-6072-ga3a821c903c9fa2288712d31da2038d0297babcb (so I wonder why this
isn't a 8/9/10 Regression).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
the file from icu 65.1 is built using
g++ -v -Wdate-time -g -O3 -fstack-protector-strong -Wformat -Werror
=format-security -W -Wall -pedantic -Wpointer-arith -Wwrite-strings
-Wno-long-long -std=c++11 -c -o genmbcs.o genmbcs.ii
no specific patches applied for the trunk. The compiler defaults to
Confirmed. With the options in Comment 4, I'm able to recreate the
hang/infinite loop. I'll have a look.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler
So we are in an infinite loop in process_address() calling
process_address_1(). I've hacked in some code to ICE if we loop for too
long and I'm currently using creduce to minimize the test case.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I cannot recreate this with trunk or GCC 9 from today. DO you have
extra patches applied or ???
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053
Title:
Compiler gets stuck
Here's the minimal test case using options -O3 -mcpu=power8 -fstack-
protector-strong:
void bar();
char b;
void
foo (void)
{
char a;
int d = b;
char *e =
while (d)
*e++ = --d;
bar ();
}
--
You received this bug notification because you are a member of Desktop
Packages, which is
This bug was fixed in the package ghostscript - 9.50~dfsg-5ubuntu1
---
ghostscript (9.50~dfsg-5ubuntu1) focal; urgency=medium
* Re-introduced exception rule for building with only -O2 instead
of -O3 on ppc64el (see also LP: #1862053).
-- Till Kamppeter Fri, 7 Feb 2020
Launchpad has imported 3 comments from the remote bug at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93658.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: GCC Bugzilla #93658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93658
** Also affects: gcc via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93658
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Debian is not using the exception rule for not using -O3 on ppc64el in
their Ghostscript package, simply due to the fact that the whole Debian
is done with -O2 by default, on all architectures.
Are there also problems with -O3 on ppc64el with other packages than
Ghostscript? Should we perhaps use
Found that Ubuntu's Ghostscript had already an exception rule for not
using -O3 on ppc64el which got lost with the sync. Re-introducing it and
reporting to Debian ...
** Changed in: ghostscript (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you
** Also affects: ghostscript (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ghostscript (Ubuntu)
Status: New => Triaged
** Changed in: ghostscript (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
32 matches
Mail list logo
