LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 1063 - test/Regression/Transforms/InstCombine/2006-04-01-InfLoop fails on amd64
Summary: test/Regression/Transforms/InstCombine/2006-04-01-InfLoop fails on amd64
Status: RESOLVED FIXED
Alias: None
Product: libraries
Classification: Unclassified
Component: Transformation Utilities (show other bugs)
Version: trunk
Hardware: PC Linux
: P normal
Assignee: Unassigned LLVM Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-20 20:20 PST by Chandler Carruth
Modified: 2010-02-22 12:49 PST (History)
1 user (show)

See Also:
Fixed By Commit(s):

Attachments
output from llvm-upgrade (19.32 KB, application/octet-stream)
2006-12-20 20:22 PST, Chandler Carruth 		Details
llvm-as output (5.11 KB, application/octet-stream)
2006-12-20 20:22 PST, Chandler Carruth 		Details
opt output -- from GDB (3.65 KB, application/octet-stream)
2006-12-20 20:23 PST, Chandler Carruth 		Details
Detailed run output, shows the inf loop (13.40 KB, application/octet-stream)
2006-12-20 20:24 PST, Chandler Carruth 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chandler Carruth 2006-12-20 20:20:58 PST 
test/Regression/Transforms/InstCombine/2006-04-01-InfLoop.ll failure on amd64,
on LLVM being built with gcc 3.4.6

A snippet of the run output is below, with more detailed output in attachments.

-Chandler
Comment 1 Chandler Carruth 2006-12-20 20:22:18 PST 
Created attachment 527 [details]
output from llvm-upgrade
Comment 2 Chandler Carruth 2006-12-20 20:22:50 PST 
Created attachment 528 [details]
llvm-as output
Comment 3 Chandler Carruth 2006-12-20 20:23:29 PST 
Created attachment 529 [details]
opt output -- from GDB
Comment 4 Chandler Carruth 2006-12-20 20:24:04 PST 
Created attachment 530 [details]
Detailed run output, shows the inf loop
Comment 5 Chris Lattner 2006-12-22 16:29:24 PST 
Was this fixed by using a different version of GCC?  If so, it's likely a gcc miscompilation.
Comment 6 Chandler Carruth 2007-01-04 00:11:27 PST 
This is fixed by compiling LLVM and LLVM-GCC with GCC 4.0.3, rather than 4.1.1,
so likely a miscompilation...