Browse Prior Art Database

System and Method to Mark and Handle Dirty IL to Avoid Compiler ICE

IP.com Disclosure Number: IPCOM000222613D
Publication Date: 2012-Oct-19
Document File: 8 page(s) / 173K

Publishing Venue

The IP.com Prior Art Database

Abstract

ICE(Internal Compiler Error) is an unrecoverable and fatal error occurred when compiling programs indicating the compiler crashed causing compiling abend, no executable produced!!! IL(Intermediate Language) is well-defined intermediate representation/instructions that compiler front-end produces, back-end accepts it as input and outputs the machine code. Dirty IL is a block of intermediate instructions which violates the expected compiler behavior, and ICE-prone.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 61% of the total text.

Page 01 of 8

System and Method to Mark and Handle Dirty IL to Avoid Compiler ICE

When ICE occurred we won't have any executables for running and users have to wait for long time fixing.

Known Solutions:

Current compiler systems have designed some features to provide basic error information of source where ICE occurred, while most of them focus on

locating.

If we can find a way, that keeps the unaffected business compiling and running smoothly even if ICE occurred within the whole application, users won't be

worried about that their primary business may stop any more!

Our invention is shown below:

1


Page 02 of 8

We implement an ICE handler, which can generate a runnable trial binary and contain runtime report.

Core idea:

When ICEs are detected during compiling, recovery system will be enabled, then the dirty IL will be marked. Runtime warning instructions that report application
risks are inserted when encounting dirty IL.

2


Page 03 of 8

Advantages/Business impact:

To users:


- Save efforts and time when troubled into ICE.


- If someone is troubled into ICE, he/she is able to get an executable prototype to test without waiting for the patch. To company:


- Save efforts and time for fixing the ICE problem


- Low cost of implementation, least impact on compilation process


- Increase user experience and friendliness


-An innovative perspective to run business though ICE occurred within the beta application, and improve the development life cycle for both users and developers.


- A lig...