Jack Howarth wrote:
Has anyone ever run the libffi testsuite when built at
-m64 on Darwin PPC? It appears that every single test fails
at -m64 on execution.
Jack
Sigh, I can't resist!
There is _NO_ 64-bit libffi port for darwin ppc.
"Erich Plondke" <[EMAIL PROTECTED]> wrote on 20/09/2006 04:09:14:
> On 9/19/06, Erich Plondke <[EMAIL PROTECTED]> wrote:
> > On 9/19/06, Ira Rosen <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > Does this patch fix the problem?
> >
> > Well... seems pretty good. I get the instruction generated
On Aug 18, 2006, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> Geoffrey Keating <[EMAIL PROTECTED]> writes:
>> On 18/08/2006, at 5:42 PM, Ian Lance Taylor wrote:
>> > We could avoid nesting memcpy calls on ACCUMULATE_OUTGOING_ARGS
>> > machines, in which case I think Alex's patch is unnecessary.
On Sep 18, 2006, Roman Kononov <[EMAIL PROTECTED]> wrote:
> Merge can be safely done like this:
> If both functions A and B are not inlined functions, and they have
> single entry points, and memcmp of their asm code is zero, and the
> code is large enough, then the asm code of the functions B is
Okay, I mispoke...not every test fails on
Darwin PPC at -m64...
=== libffi Summary for unix/-m32 ===
# of expected passes1068
# of expected failures 8
# of unsupported tests 8
=== libffi Summary for unix/-m64 ===
# of expected pa
Has anyone ever run the libffi testsuite when built at
-m64 on Darwin PPC? It appears that every single test fails
at -m64 on execution.
Jack
On Tue, Sep 19, 2006 at 11:30:40AM -0400, Kate Minola wrote:
> Ok, I say to myself, I understand this. The version of g++ that I am
> using is one that I built in my home directory and so it's libgcc_s.so.1
> is only linked if I use -static-libgcc. Whereas without -static-libgcc,
> I am linking w
Perhaps a kind person would help clear up my confusion regarding
-static-libgcc?
Consider the following C++ program:
foo.cc -
using namespace std;
#include
int main (int argc, char *argv[])
{
int DIGITS;
DIGITS=14;
pow(1./10,DIGITS);
return 0;
}
---
On Tuesday 19 September 2006 06:49, Chandan_Gupta-r65863 wrote:
> Hi
>
> I am doing the assembly coding in ARM7TDMI and using the GNU Assembler.
> In GNU ARM Assembler Quick Reference, I found 2 register Names which I
> am not able to understand, they are ip & fp.
ip is r12 and fp r11.
Paul
On 19 September 2006 13:16, Rohit Arul Raj wrote:
> Hi all,
>
> I am upgrading a cross compiler from gcc 3.4.6 to gcc 4.1.1.
>
> i just want to confirm whether the poisoned macro
> FUNCTION_ARG_PASS_BY_REFERENCE in target.h is replaced by the target
> hook in target.c as TARGET_PASS_BY_REFERENC
Hi all,
I am upgrading a cross compiler from gcc 3.4.6 to gcc 4.1.1.
i just want to confirm whether the poisoned macro
FUNCTION_ARG_PASS_BY_REFERENCE in target.h is replaced by the target
hook in target.c as TARGET_PASS_BY_REFERENCE.
Is there any log file other than ChangeLog which keeps the l
Hi,
Does this patch fix the problem?
Ira
Index: tree-vect-transform.c
===
--- tree-vect-transform.c (revision 117002)
+++ tree-vect-transform.c (working copy)
@@ -1916,10 +1916,10 @@ vectorizable_load (tree stmt, block_s
12 matches
Mail list logo