Displaying 7 results from an estimated 7 matches for "target_64bit".
2005 Jan 03
0
[LLVMdev] [patch] native AMD64 support
...E | MASK_MMX | MASK_128BIT_LONG_DOUBLE);
> ix86_fpmath = FPMATH_SSE;
> +#endif
> }
> else
> {
> @@ -2795,7 +2801,8 @@
> tree f_gpr, f_fpr, f_ovf, f_sav, record, type_decl;
>
> /* For i386 we use plain pointer to argument area. */
> - if (!TARGET_64BIT)
> + /* LLVM also uses the i386 standard version in 64-bit mode */
> + if (!TARGET_64BIT || EMIT_LLVM)
> return build_pointer_type (char_type_node);
>
> record = (*lang_hooks.types.make_type) (RECORD_TYPE);
> @@ -2858,7 +2865,8 @@
> int stdarg_p;
> int i;
&...
2012 Mar 23
3
[LLVMdev] DragonEgg 3.0 with GCC 4.7
.../builddir/build/BUILD/dragonegg-3.0.src/src/DefaultABI.cpp: In member function 'void DefaultABI::HandleArgument(tree, std::vector<llvm::Type*, std::allocator<llvm::Type*> >&, llvm::Attributes*)':
/builddir/build/BUILD/dragonegg-3.0.src/src/DefaultABI.cpp:223:14: error: 'TARGET_64BIT' was not declared in this scope
In file included from /usr/lib/gcc/x86_64-redhat-linux/4.7.0/plugin/include/tm_p.h:5:0,
from /builddir/build/BUILD/dragonegg-3.0.src/src/Constants.cpp:52:
/usr/lib/gcc/x86_64-redhat-linux/4.7.0/plugin/include/tm-preds.h:191:13: error: use of enu...
2008 Dec 28
1
[LLVMdev] LLVM ARM Cross-Compiler Build
...refix=/usr/local --enable-checking
--enable-llvm=../../llvm/objdir/ --disable-bootstrap --disable-multilib
--program-prefix=llvm- --target=arm-linux-gnu --enable-languages=c,c++,objc
$ make; make install
Compiler errors are caused due to absence of definition of macros:
MACHO_DYNAMIC_NO_PIC_P, TARGET_64BIT, and so on.
When these macros are manually added, it caused another error, like below:
../objdir/./gcc/xgcc -B../objdir/./gcc/ -B/usr/local/arm-linux-gnu/bin/
-B/usr/local/arm-linux-gnu/lib/ -isystem /usr/local/arm-linux-gnu/include
-isystem /usr/local/arm-linux-gnu/sys-include -O2 -O2 -g -O2 -...
2008 Feb 27
1
[LLVMdev] ABI for i128 on x86-32?
> See ix86_return_in_memory. (In 4.3 this is renamed to
> return_in_memory_32.)
> i128==TImode.
But TImode should be used for __m128 stuff only there, not for integers.
I'm looking into gfortran now.
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2008 Dec 30
0
[LLVMdev] LLVM ARM Cross-Compiler Build
...ecking
> --enable-llvm=../../llvm/objdir/ --disable-bootstrap --disable-multilib
> --program-prefix=llvm- --target=arm-linux-gnu --enable-languages=c,c++,objc
> $ make; make install
>
> Compiler errors are caused due to absence of definition of macros:
> MACHO_DYNAMIC_NO_PIC_P, TARGET_64BIT, and so on.
>
I've reproduced the same error on my x86/Linux system (the first macro is
undefined). I suspect if I go ahead and also add it, I'll continue to the
next error you found. One might guess that since this cross-tool build is
so broken, that it's likely not used by the f...
2008 Dec 28
4
[LLVMdev] [Patch] Adding unit tests to LLVM
Mark Kromis wrote:
> On Dec 27, 2008, at 7:41 PM, Misha Brukman wrote:
>> 2008/12/27 Mark Kromis <greybird at mac.com>
>> Just a curiosity question, why push for gtest vs Boost Test or a
>> different test suite?
>> I normally use Boost, and their test suite, so I'm more familiar with
>> that. So I was wondering is one better then the other, or is it
2010 Aug 16
3
[LLVMdev] -fomit-frame-pointer on intel darwin
Can anyone shed some light on the origins of the comments...
/* Mach-O doesn't support omitting the frame pointer for now. */
...in gcc/config/i386/i386.c. FSF gcc trunk has enabled the
omit-frame-pointer option as the default for both i386 and x86_64
recently.
* config.gcc: Handle --enable-frame-pointer.
* configure.ac: Add --enable-frame-pointer.
* configure: Regenerated.
*