6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-08-17 05:29:24 +00:00
Code Issues Projects Releases Wiki Activity

Dan is right, using "string first" would produce false positives. So,

Browse Source 
devolve the check to a comparison against each component in the string.
Fortunately there isn't many of them.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@36376 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Reid Spencer 2007-04-23 21:21:53 +00:00
parent 703f5291c4
commit 4f6e9ab3d7
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
test/lib/llvm.exp
View File

@ -207,13 +207,15 @@ proc llvm_gcc_supports { lang } {
fortran { set file fcc1 } fortran { set file fcc1 }
default { return 0 } default { return 0 }
} }
if { [ string first "$lang" "$llvmgcc_langs" ] >= 0 } { foreach supported_lang [split "$llvmgcc_langs" ,] {
# FIXME: Knowing it is configured is not enough. We should do two more if { "$lang" == "$supported_lang" } {
# checks here. First, we need to run llvm-gcc -print-prog-name=$file to get # FIXME: Knowing it is configured is not enough. We should do two more
# the path to the compiler. If we don't get a path, the language isn't # checks here. First, we need to run llvm-gcc -print-prog-name=$file to
# properly configured or built. If we do get a path, we should check to make # get the path to the compiler. If we don't get a path, the language isn't
# sure that it is executable and perhaps even try executing it. # properly configured or built. If we do get a path, we should check to
return 1; # make sure that it is executable and perhaps even try executing it.
return 1;
}
} }
return 0; return 0;
} }