llvm dev - May 2011 - [LLVMdev] cygwin build broken (X86ISelDAGToDAG.cpp: ‘LOCK_OR8mi’ is not a member of ‘llvm::X86’)

On 5/17/2011 2:58 AM, Eric Christopher wrote:
> On May 14, 2011, at 3:08 AM, Eric Niebler wrote:
> 
>> Just a heads up that the llvm build appears to be broken on cygwin. I
>> haven't investigated, but here's the failures:
>>
>> llvm[3]: Compiling X86ISelDAGToDAG.cpp for Release+Asserts build
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1487:
>> error: ‘LOCK_OR8mi’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1488:
>> error: ‘LOCK_OR8mr’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1489:
>> error: ‘LOCK_OR16mi8’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1490:
>> error: ‘LOCK_OR16mi’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1491:
>> error: ‘LOCK_OR16mr’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1492:
>> error: ‘LOCK_OR32mi8’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1493:
>> error: ‘LOCK_OR32mi’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1494:
>> error: ‘LOCK_OR32mr’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1495:
>> error: ‘LOCK_OR64mi8’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1496:
>> error: ‘LOCK_OR64mi32’ is not a member of ‘llvm::X86’
>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1497:
>> error: ‘LOCK_OR64mr’ is not a member of ‘llvm::X86’
>>
> 
> This should be part of a rebuilt compiler. Are you still seeing this? Can
you try a clean build to make sure there's not a missing dependency
somewhere if so?
Still seeing this. I'm fully synced. I nuked my build directory. Ran
configure --enable-optimized. Ran make. Same problem.

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com

On May 17, 2011, at 2:50 AM, Eric Niebler wrote:
> On 5/17/2011 2:58 AM, Eric Christopher wrote:
>> On May 14, 2011, at 3:08 AM, Eric Niebler wrote:
>> 
>>> Just a heads up that the llvm build appears to be broken on cygwin.
I
>>> haven't investigated, but here's the failures:
>>> 
>>> llvm[3]: Compiling X86ISelDAGToDAG.cpp for Release+Asserts build
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1487:
>>> error: ‘LOCK_OR8mi’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1488:
>>> error: ‘LOCK_OR8mr’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1489:
>>> error: ‘LOCK_OR16mi8’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1490:
>>> error: ‘LOCK_OR16mi’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1491:
>>> error: ‘LOCK_OR16mr’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1492:
>>> error: ‘LOCK_OR32mi8’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1493:
>>> error: ‘LOCK_OR32mi’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1494:
>>> error: ‘LOCK_OR32mr’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1495:
>>> error: ‘LOCK_OR64mi8’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1496:
>>> error: ‘LOCK_OR64mi32’ is not a member of ‘llvm::X86’
>>>
/home/Eric/boost/consulting/svn/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:1497:
>>> error: ‘LOCK_OR64mr’ is not a member of ‘llvm::X86’
>>> 
>> 
>> This should be part of a rebuilt compiler. Are you still seeing this?
Can you try a clean build to make sure there's not a missing dependency
somewhere if so?
> 
> Still seeing this. I'm fully synced. I nuked my build directory. Ran
> configure --enable-optimized. Ran make. Same problem.
What does your <build>/lib/Target/X86/X86GenInstrNames.inc file look like?
Are the LOCK_OR* bits in there?

After last night I'd also expect you'd be missing LOCK_XOR* and
LOCK_AND*?

-eric

On 5/18/2011 1:47 AM, Eric Christopher wrote:
> On May 17, 2011, at 2:50 AM, Eric Niebler wrote:
>> On 5/17/2011 2:58 AM, Eric Christopher wrote:
>>> On May 14, 2011, at 3:08 AM, Eric Niebler wrote:
>>>
>>>> Just a heads up that the llvm build appears to be broken on
cygwin. I
>>>> haven't investigated, but here's the failures:
<snip>
>>>
>>> This should be part of a rebuilt compiler. Are you still seeing
this? Can you try a clean build to make sure there's not a missing
dependency somewhere if so?
>>
>> Still seeing this. I'm fully synced. I nuked my build directory.
Ran
>> configure --enable-optimized. Ran make. Same problem.
> 
> What does your <build>/lib/Target/X86/X86GenInstrNames.inc file look
like? Are the LOCK_OR* bits in there?
User error! I had previously run CMake in the source directory, and it
left turd files scattered everywhere (including a turd
X86GenInstrNames.inc alongside X86.h). For some reason, 'svn status' is
lying to me about what's under version control and what isn't, so I have
to nuke the whole thing and start over. :-/

Sorry for the noise.

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com