[LLVMbugs] [Bug 4552] New: Error: bad register name `%dil'
bugzilla-daemon at cs.uiuc.edu
bugzilla-daemon at cs.uiuc.edu
Mon Jul 13 19:52:07 PDT 2009
http://llvm.org/bugs/show_bug.cgi?id=4552
Summary: Error: bad register name `%dil'
Product: new-bugs
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: new bugs
AssignedTo: unassignedbugs at nondot.org
ReportedBy: regehr at cs.utah.edu
CC: llvmbugs at cs.uiuc.edu
Seen on Ubuntu Hardy on x86.
regehr at john-home:~/volatile/tmp168$ llvm-gcc -O3 small.c
/tmp/ccApvYXi.s: Assembler messages:
/tmp/ccApvYXi.s:184: Error: bad register name `%dil'
regehr at john-home:~/volatile/tmp168$ llvm-gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure
--prefix=/home/regehr/z/tmp/llvm-gcc-r75580-install
--program-prefix=llvm-r75580- --enable-languages=c,c++
--enable-llvm=/home/regehr/z/tmp/llvm-r75580 --enable-checking=release
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5646) (LLVM build)
regehr at john-home:~/volatile/tmp168$ cat small.c
char
safe_mod_func_char_s_s (char _si1, char _si2)
{
return 1 ? _si1 : +1;
}
char
safe_mod_func_int_s_s (int _si1, char _si2)
{
return -32767 - 1 ? _si1 : +1;
}
char
safe_add_func_char_u_u (char _ui1, char _ui2)
{
}
char
safe_mul_func_char_u_u (char _ui1, char _ui2)
{
return _ui1 * _ui2;
}
int g_8;
int g_72;
uint84 (int p_15, char p_17, char p_19)
{
for (1; 1; safe_add_func_char_u_u)
{
func_40 (1);
for (1; g_8 <= 0; g_8 = 1)
{
}
}
}
int
func_21 (int16p_22)
{
int l_23 = 0xC477L;
return l_23;
}
int
func_40 (int p_41, int p_42, int p_43, int p_45)
{
func_55 (~1);
func_55 (1);
}
char
func_51 (int64p_52)
{
return g_8;
}
int
func_55 (int16p_56)
{
if (safe_mod_func_int_s_s
(safe_mul_func_char_u_u (func_51 (1), func_70 (!1)), 0))
if (func_21 (1) & safe_mod_func_char_s_s (g_72, 0))
return 1;
g_72 = 1;
}
int
func_70 (int p_71, int p_73)
{
char l_74;
l_74 = g_72;
return l_74;
}
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list