https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
Benda Xu changed:
What|Removed |Added
CC||heroxbd at sohu dot com
--- Comment #18 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
Ramana Radhakrishnan changed:
What|Removed |Added
Status|REOPENED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #16 from Tyrel Haveman ---
Certainly that is an option in many cases. In my particular case this is
building on an OpenStack cloud instance and we've maxed out the resources we've
paid for, so I don't have the room to add swap space o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #15 from dave.anglin at bell dot net ---
On 2016-01-25 11:18 AM, tyrel at kulshanconcepts dot com wrote:
> Is there a flag I can add to `configure` or anything else I might be able to
> do
> to work around this issue so that I can get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #14 from Tyrel Haveman ---
Is there a flag I can add to `configure` or anything else I might be able to do
to work around this issue so that I can get my builds going? Not being able to
build GCC is blocking a lot of other work here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #13 from Tyrel Haveman ---
(In reply to ktkachov from comment #12)
> Seems the division reservations on the other automata still cause too much
> state space explosion.
> Perhaps reducing the reservation durations on the division rese
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
Tyrel Haveman changed:
What|Removed |Added
CC||tyrel at kulshanconcepts dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
Sven Schumacher changed:
What|Removed |Added
CC||schumacher at wedia dot de
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #9 from Bernd Edlinger ---
The patch works for me.
Thanks for fixing this so quickly!
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #7 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Fri Apr 4 15:47:45 2014
New Revision: 209119
URL: http://gcc.gnu.org/viewcvs?rev=209119&root=gcc&view=rev
Log:
[ARM/AArch64] Reduce divider reservation duration in Cortex-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
Andrew Pinski changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
--- Comment #6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #4 from ktkachov at gcc dot gnu.org ---
(In reply to Bernd Edlinger from comment #3)
> Kyrill,
>
> sorry, to bother you with this,
> but do you see any possibility to
> return to the previous memory footprint?
I'll have a look.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
Bernd Edlinger changed:
What|Removed |Added
CC||ktkachov at gcc dot gnu.org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #2 from Bernd Edlinger ---
started with r208910 of gcc/config/arm/cortex-a53.md
as it looks like, this single check-in did almost double the memory usage!
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60743
--- Comment #1 from Bernd Edlinger ---
current snapshot gcc-4.9-20140330, trunk revision 208948
uses 773 MB peak memory.
last week's snapshot gcc-4.9-20140323, trunk revision 208775
used only 417 MB peak memory, which did not cause problems.
18 matches
Mail list logo
