Displaying 4 results from an estimated 4 matches for "haxor".
Did you mean:
hax0r
2004 Nov 16
0
[LLVMdev] Fixes for windows version
...mitted by gcc from one version to another. I see where this is
> handled (llvm/ADT/hash_map), but it isn't clear how to add support for
> VC++ to the auto config magic.
Yeah, there's tests in autoconf/m4/cxx_hash_map to dictate which naming
style needs to be used. You'll have to haxor it in there if you're not
using the configure script.
>
> I'll soon thoroughly go through the llvm_test results for FreeBSD to
> identify all platform dependencies that cause failures. I'm getting far
> more failures than I have in the past, though it's apparent many...
2004 Nov 16
2
[LLVMdev] Fixes for windows version
...e version to another. I see where this is
>>handled (llvm/ADT/hash_map), but it isn't clear how to add support for
>>VC++ to the auto config magic.
>
> Yeah, there's tests in autoconf/m4/cxx_hash_map to dictate which naming
> style needs to be used. You'll have to haxor it in there if you're not
> using the configure script.
I created a special configure project in the Visual Studio solution
which uses sed to directly enter the correct configuration values for
the Visual Studio build. It seems quite unnecessary to have all the auto
detection stuff work...
2004 Nov 16
2
[LLVMdev] Fixes for windows version
I have some patches of my own:
* An improvement on Morten's fix to Signals.cpp.
* Undo the breakage to system.vcproj (Signals.cpp was being built twice
as a result).
* Fix a class/struct inconsistency.
* Remove unneeded #includes from win32 fSystem files.
I've also determined why VC++ complains about deprecated destructors
when using hash_map. Because it's not ANSI (yet),
2004 Nov 16
0
[LLVMdev] Fixes for windows version
...see where this is
> >>handled (llvm/ADT/hash_map), but it isn't clear how to add support for
> >>VC++ to the auto config magic.
> >
> > Yeah, there's tests in autoconf/m4/cxx_hash_map to dictate which naming
> > style needs to be used. You'll have to haxor it in there if you're not
> > using the configure script.
>
> I created a special configure project in the Visual Studio solution
> which uses sed to directly enter the correct configuration values for
> the Visual Studio build. It seems quite unnecessary to have all the au...