Displaying 11 results from an estimated 11 matches for "defaultabi".
2011 Jul 19
3
[LLVMdev] dragonegg svn still broken
On 18 July 2011 15:23, David Blaikie <dblaikie at gmail.com> wrote:
> Looks like that break came
> from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154
> Judging by this ArrayRef ctor you should be able to simplify those calls by
> changing the last two arguments from "&foo, 1" to, simply, "foo".
I've done this in r135472.
Jay.
2011 Jul 19
0
[LLVMdev] dragonegg svn still broken
...changing the last two arguments from "&foo, 1" to, simply, "foo".
>
> I've done this in r135472.
>
> Jay.
Jay,
I don't know if this is from a new commit but at r135473, dragonegg svn
fails to compile against FSF gcc 4.5.3 with the error...
Compiling DefaultABI.cpp
/sw/src/fink.build/dragonegg-gcc45-3.0-1/dragonegg-3.0/src/DefaultABI.cpp:194:18: error: use of undeclared identifier 'OpaqueType'
Type *OpTy = OpaqueType::get(getGlobalContext());
^
Jack
2012 Mar 23
3
[LLVMdev] DragonEgg 3.0 with GCC 4.7
...;m getting are:
/builddir/build/BUILD/dragonegg-3.0.src/src/Trees.cpp: In function 'uint64_t getFieldOffsetInBits(tree)':
/builddir/build/BUILD/dragonegg-3.0.src/src/Trees.cpp:191:56: error: 'BITS_PER_UNIT' was not declared in this scope
/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 fi...
2010 Mar 04
1
[LLVMdev] Struct parameter
Hi, guys,
If there is a struct {i8, i8, i32}, and there are several parameter
GPRs(32bits), say, r0, r1~r5, I can make this struct to be passed in r0, r1
because LLVM_SHOULD_PASS_AGGREGATE_IN_INTEGER_REGS is true in DefaultABI,
neither it passed by value, nor it passed as FCA.
But if the first parameter register r0 is occupied by other argument, in
DefaultABI, that struct passed as a i64, and i64 requires 8 bytes alignment
in my target, therefore, r1 is skipped for this reason, this is not what I
want.
I have tried to p...
2011 Jul 11
1
[LLVMdev] type-system-rewrite branch landing tomorrow
...e recursion when we use llvm-gcc for arm-target.
Because return type of function pointer p's is struct type T which has one element,
llvm-gcc for arm target calls a function which tries to chang aggregate return type
to inner element.
(For example, C.HandleAggregateResultAsScalar(Ty);
--> DefaultABI::HandleReturnType() function gcc/llvm-abi-default.cpp)
In this case, infinite recursion is generated.
So I made a patch.
when function's return type is struct type and this struct type includes only
function's pointer type as element, funtion's return type is not struct type's el...
2008 Mar 26
0
[LLVMdev] Wrong calling convention?
...on hearing ideas about how to determine how a
>> function returns a small struct, without knowing the internals of the
>> struct.
> Take a look at llvm-gcc. Look for HandleAggregateShadowArgument.
This does not qualify as "without knowing the internals of the struct"
:-)
DefaultABI::HandleReturnType made an interesting reading, although it
uses information which is unaccessible to my compiler.
--
Oscar
2008 Mar 26
3
[LLVMdev] Wrong calling convention?
Take a look at llvm-gcc. Look for HandleAggregateShadowArgument.
Evan
On Mar 26, 2008, at 10:31 AM, Óscar Fuentes wrote:
> Óscar Fuentes <ofv at wanadoo.es> writes:
>
>> BTW, -fpcc-struct-return solves the case that motivated this thread.
>
> -fpcc-struct-return is an ABI change, hence it requires "compiling the
> world". Not acceptable.
>
> I'll
2011 Jul 09
2
[LLVMdev] type-system-rewrite branch landing tomorrow
On Sat, Jul 9, 2011 at 4:27 PM, Chris Lattner <clattner at apple.com> wrote:
> I'm sorry, I've been away from the computer. I'll investigate this in the next half hour. Thanks for the test cases!
One more testcase, which might be of interest; crashes clang on x86-64:
struct T {
struct T (*p)(void);
} t;
-Eli
2011 Jul 10
0
[LLVMdev] type-system-rewrite branch landing tomorrow
On Jul 9, 2011, at 4:35 PM, Eli Friedman wrote:
> On Sat, Jul 9, 2011 at 4:27 PM, Chris Lattner <clattner at apple.com> wrote:
>> I'm sorry, I've been away from the computer. I'll investigate this in the next half hour. Thanks for the test cases!
>
> One more testcase, which might be of interest; crashes clang on x86-64:
>
> struct T {
> struct T
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...w/opt/llvm-3.2/include -fPIC -fvisibility-inlines-hidden -g -Wall -W -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -Wcovered-switch-default -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS \
Aliasing.o Backend.o Cache.o ConstantConversion.o Convert.o Debug.o DefaultABI.o Trees.o TypeConversion.o bits_and_bobs.o Target.o \
-lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMMCParser -lLLVMCodeGen -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMInstrumentation -lLLVMAsmParser -lLLVMBitWriter -lLL...
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
Jack,
I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message:
dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1
means the initializer called something which