Bug 189876 - gcc dies with internal compiler error
Summary: gcc dies with internal compiler error
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: powerpc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-25 13:51 UTC by Nils Philippsen
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-04-26 09:37:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
preprocessed source of the offending file (732.07 KB, text/plain)
2006-04-25 13:59 UTC, Nils Philippsen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 27260 0 None None None Never

Description Nils Philippsen 2006-04-25 13:51:41 UTC
Description of problem:

While building an update for sane-backends, gcc died with an internal compiler
error when compiling plustek-pp_motor.c.

Version-Release number of selected component (if applicable):
gcc-4.1.0-10

How reproducible:
Reproducible.

Steps to Reproduce:
1. checkout sane-backends-1.0.17-9 from dist CVS/devel
2. build on ppc
  
Actual results:
"""
plustek-pp_motor.c: In function 'motorP96FillHalfStepTable':
plustek-pp_motor.c:1541: internal compiler error: in expand_expr_real_1, at
expr.c:6750
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/cc3eNbPd.out file, please attach this to
your bugreport.
"""

Expected results:
no internal compiler error

Additional info:

Comment 2 Nils Philippsen 2006-04-25 13:59:19 UTC
Created attachment 128200 [details]
preprocessed source of the offending file

Comment 3 Nils Philippsen 2006-04-25 14:01:17 UTC
btw, works fine on FC5 with gcc-4.1.0-3

Comment 4 Nils Philippsen 2006-05-03 07:22:21 UTC
fixed in gcc-4.1.0-12


Note You need to log in before you can comment on or make changes to this bug.