Bug 11537 - internal error when compiling pine on alpha
Summary: internal error when compiling pine on alpha
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: c (show other bugs)
Version: 3.3.1
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-16 05:30 UTC by Robert Skorvan
Modified: 2005-07-23 22:49 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Skorvan 2003-07-16 05:30:37 UTC
I am running Debian Sarge (testing) on a 166mhz alpha noname
I was compiling the source for pine-4.44-8 (the pine source .deb version)

Output when it got up to compiling other.c:

gcc -O2  -g  -DENABLE_LDAP -DLNX -DSYSTYPE=\"LNX\" -DMOUSE   -c -o other.o 
other.c
other.c: In function `toggle_feature_bit':
other.c:11218: warning: cast to pointer from integer of different size
other.c:11231: warning: cast to pointer from integer of different size
other.c:11236: warning: cast to pointer from integer of different size
Internal compiler error: Error reporting routines re-entered.
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
Comment 1 Falk Hueffner 2003-07-16 06:38:25 UTC
Please provide the preprocessed source, as described at the URL given in the
error message. Also, what gcc version are you using?
Comment 2 Robert Skorvan 2003-07-17 03:00:16 UTC
This is using gcc-3.3.1 (the debian sarge version for alpha)

For some reason when I compiled it again, it didn't have an internal compiler 
error.

I think it may just be to do with sarge... i've noticed some seg faults in 
other programs aswell.

Should I still provide the preprocessed source?
Comment 3 Andrew Pinski 2003-07-17 03:04:26 UTC
I think you should check your memory because if it fails and then passes without changing any 
thing that is a sign that your memory is bad.  I would provide the preprocessed source any way 
because if it was not your memory but something else we can check on it faster.
Comment 4 Dara Hazeghi 2003-08-24 19:17:59 UTC
Can you confirm whether you can still reproduce this problem, and if so, please include the 
preprocessed source? Thank you.
Comment 5 Andrew Pinski 2003-09-19 16:01:14 UTC
No feedback in 2 months but this is most likely a hardware problem so closing.