Bug 174792

Summary: antlr/CharScanner.java:103: internal compiler error: in gimplify_expr, at gimplify.c:3987
Product: Red Hat Enterprise Linux 4 Reporter: Andrew Cagney <cagney>
Component: gcc4Assignee: Jakub Jelinek <jakub>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: aoliva, mnewsome
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 16:08:22 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:
Bug Depends On:    
Bug Blocks: 173278, 175299    
Attachments:
Description Flags
Trivial backport of the patch that fixed the bug in mainline none

Description Andrew Cagney 2005-12-02 07:16:59 UTC 
Description of problem:

antlr/CharScanner.java: In class 'antlr.CharScanner':
antlr/CharScanner.java: In method 'antlr.CharScanner.consumeUntil(int)':
antlr/CharScanner.java:103: internal compiler error: in gimplify_expr, at
gimplify.c:3987

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


How reproducible:

100%

Steps to Reproduce:
1. download junit
2. use gcj/fastjar to build junit.jar
3. attempt gcj -c junit.car

need to reduce down to testcase, sigh
Comment 1 Jakub Jelinek 2005-12-02 10:12:38 UTC 
Step 1 is fuzzy, lacks info where to download it from...
Comment 2 Alexandre Oliva 2005-12-02 19:30:55 UTC 
Created attachment 121775 [details]
Trivial backport of the patch that fixed the bug in mainline

This patch fixes the bug by preventing labels from multiple methods to have the
same identifier, which ultimately caused them to map to the same label
declaration, such that for all but one of the methods with a label at the same
pc, the assertion check failed.
Comment 7 Jiri Pallich 2012-06-20 16:08:22 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.