From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: binutils@sourceware.cygnus.com
Subject: Re: elf32-mips breaks binary compatibility
Date: Mon, 16 Aug 1999 23:05:00 -0000 [thread overview]
Message-ID: <19990817080633.C548@mff.cuni.cz> (raw)
In-Reply-To: <19990816121931.A15491@uni-koblenz.de>
> Right now I'm working on changing the current linker to tag all binaries
> such that the dynamic linker can recognice them and do the right thing.
> Mark has suggested using a DT_MIPS_LINUX_VERSION tag. I'm a bit
> reluctant to allocate such a new DT_ tag because MIPS / SGI are using them
> for all sorts of purposes and I want to avoid a future clash. So my
> proposal which is a bit hackish would be to use the DT_MIPS_TIME_STAMP
> tag with a special magic time stamp. I've choosen the value 11717580
> which is equivalent to a date in 1970, therfore should never ever be
> generated in a binary generated by a SGI linker; current GNU linkers don't
> emit this tag at all. Comments?
With timestamp I see the problem what if quickstart is implemented in
binutils (I still would like to give it a shot on sparc64 to see if the
performance boost is worth the trouble), in which case we'll need to use
DT_MIPS_TIME_STAMP...
So IMHO DT_MIPS_LINUX_VERSION would not be very bad solution. And you could
speak with SGI to leave that number for you in the specs.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux | http://ultra.linux.cz/ | http://ultra.penguin.cz/
Linux version 2.3.13 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________
next prev parent reply other threads:[~1999-08-16 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-16 15:07 Ralf Baechle
1999-08-16 22:53 ` Ian Lance Taylor
1999-08-16 23:05 ` Jakub Jelinek [this message]
1999-08-16 23:11 ` Ian Lance Taylor
1999-08-17 1:25 ` Jakub Jelinek
1999-08-17 11:20 ` Ian Lance Taylor
1999-08-17 15:13 ` Ralf Baechle
1999-08-17 15:16 ` Ian Lance Taylor
1999-08-17 17:29 ` Ralf Baechle
1999-08-16 23:13 ` H.J. Lu
1999-08-17 15:16 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990817080633.C548@mff.cuni.cz \
--to=jj@sunsite.ms.mff.cuni.cz \
--cc=binutils@sourceware.cygnus.com \
--cc=ralf@uni-koblenz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).