Bug 37671
Summary: | RFE: gforth won't compile with gcc-2.96 | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Jeff Johnson <jbj> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 1.0 | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-02-26 22:47:23 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
Jeff Johnson
2001-04-25 19:09:08 UTC
This bug is probably due to gcc-2.96 producing incorrect code (guess based on experience with similar symptoms in other settings). Yeah, engine() couldn't be shorter... So far I've found one GCSE bug which caused engine-ditc.o to be miscompiled. With this fixed, there is some other bug which causes engine.o to be miscompiled with -fomit-frame-pointer (taking this one out fixes it). I'll dig some more. I have now tested this a little more and found that Gforts works with gcc-2.96 on Intel if it is configured with --enable-force-reg. I found that I get a good result (correct and fast code) with gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81) by configuring in the following way: CC="gcc -fno-gcse" ./configure --enable-force-reg --enable-indirect-threaded I will look into the generated code for the crashing versions soon. The compiler included in Red Hat Linux 7.1 and later versions of Red Hat Linux compiles gforth-5.0 correctly. The errata compiler for Red Hat Linux 7.0 (gcc-2.96-85) also compiles gforth-5.0 correctly. |