This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.


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

Re: Accessing section attributes from assembly (or C)




Beware.  In porting my MRI code, I found the MRI Compatibility Mode in the
linker to be somewhat of a misnomer and also misleading.  Sure, ld supports a
few MRI commands, but there are too many unsupported (or ignored) commands.  Any
significant MRI project will encounter these unsupported commands, and
work-arounds don't exist.  In my opinion, there is no MRI Compatibility Mode.

This incompatibility was probably better for me in the long run, though, because
it forced me to learn ld's native command language.  Now I use the native
command language exclusively (and happily).    :-)

Joe

And don't tell me there isn't one bit of difference between null and space,
because that's exactly how much difference there is.  :-)
   --- Larry Wall






Ola Liljedahl <olli@enea.se> on 07/05/2000 09:16:13 AM

To:   Michael Sokolov <msokolov@ivan.harhan.org>
cc:   chris@bahns.com, crossgcc@sourceware.cygnus.com (bcc: Joseph
      Taylor/Inter-Tel)

Subject:  Re: Accessing section attributes from assembly (or C)



MRI == Microtec
A cross compiler tool chain for embedded systems popular enough for
gcc (or is it the binutils assembler) to actually have an mri
compatibility mode. But probably the compatibility does not stretch
long enough to handle such weird relocations.
--
     Ola Liljedahl

Michael Sokolov wrote:
>
> Christopher Bahns <chris@bahns.com> wrote:
>
> > "            DC.L  (tables1_size + tables2_size)\n"
>
> Sorry, the UNIX model of an object module, which the GNU toolchain follows
just
> like any other UNIX toolchain, does not allow referencing things like the sum
> of two external symbols.
>
> > It seems that MRI can do this, but GNU
> > (as far as I know) cannot.
>
> It isn't GNU that invented this limitation, it's the UNIX way of doing things,
> of which GNU is just one implementation.
>
> As you are making comparisons with something called "MRI", you may want to
> explain what it is you are making comparisons with. To me MRI doesn't mean
> anything other than Magnetic Resonance Imaging. It seems like you are talking
> about some other compiler/assembler/linker toolchain. What sort of toolchain
is
> it? Is it used by some proprietary version of UNIX, or is it a specialized
> embedded cross-toolchain, or what?
>
> --
> Michael Sokolov         Harhan Engineering Laboratory
> Public Service Agent    International Free Computing Task Force
>                         International Engineering and Science Task Force
>                         615 N GOOD LATIMER EXPY STE #4
>                         DALLAS TX 75204-5852 USA
>
> Phone: +1-214-824-7693 (Harhan Eng Lab office)
> E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)
>
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

olli.vcf



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

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