Bug 177131
Summary: | ppc: itext.jar -> .jar.so compilation uses too much memory | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Overholt <overholt> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | aph, fitzsim, green, tromey |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | powerpc | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-01 20:34:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Overholt
2006-01-06 16:01:39 UTC
(In reply to comment #0) > Also, I doubt this happens on > i386 or Anthony probably would not have submitted his SRPMs for Extras. I did > not try to reproduce on i386 yet, though. > Don't be so sure! :-) I had my system RPM optimization flags set to -O0, since I've been doing so much debugging recently. I'm going an optimized build now and it's getting fat and slow. If I modify this to be a noarch RPM, will people have problems upgrading when we switch it over to a native RPM? I seem to remember yum having problems with this. (In reply to comment #1) > If I modify this to be a noarch RPM, will people have problems upgrading when we > switch it over to a native RPM? I seem to remember yum having problems with this. > I'm pretty sure these all got fixed. Tom Fitzsimmons would know for sure. Tom? Go to aot-compile-rpm and revise these numbers downwards: MAX_CLASSES_PER_JAR = 1024 MAX_BYTES_PER_JAR = 2097152 Tell us what you find. (In reply to comment #1) > I'm going an optimized build now and it's getting fat and > slow. It eventually finished OK (x86 w/ optimization). (In reply to comment #3) > Go to aot-compile-rpm and revise these numbers downwards: > > MAX_CLASSES_PER_JAR = 1024 > MAX_BYTES_PER_JAR = 2097152 > > Tell us what you find. I forgot to post here: I tried lower numbers ((512, 0), (1024, 512)) and it worked in both cases. Shall I try other combinations? No. It works, it's good enough. Cool, closing. |