This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [APPROVE?] Fix MIPS and PowerPC with GCC 3.x


>>>>> "Gary" == Gary Thomas <gary at mlbassoc dot com> writes:

    Jifl> This would be similar to the various hal_mk_defs.c's
    Jifl> floating around, although they requires knowledge of asm
    Jifl> syntax. Instead the C++ file can just generate the header
    Jifl> contents directly with #define's and the custom build step
    Jifl> can move it into the install tree. Something similar happens
    Jifl> for the heap magic in the memalloc package (a TCL file doing
    Jifl> the generating that time).
    >> 
    >> I don't see how your approach is going to work. We need to know how
    >> the target g++ messes about with its classes, not the host g++. Since
    >> we cannot execute a feature test program, the way to do this is to
    >> generate some assembler with the target g++ and analyse that, e.g.
    >> with a Tcl script.

    Gary> Which is exactly the problem solved by hal_mk_defs.c (albeit C
    Gary> structures instead of C++ members...)

Ah, I think I understand now. The proposal was to generate what
amounts to C code using inline asm's in C++, rather than generate real
assembler and analyse it. As opposed to hal_mk_defs.c which does
generate assembler. I guess that would work, although I am a bit
uncomfortable with mixing up languages to this extent.

Bart


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]